Landscape irrigation management with automated water budget &amp; seasonal adjust, and automated implementation of watering restrictions

ABSTRACT

Embodiments of the present invention provide methods and apparatus for water conservation with landscape irrigation controllers, plug-in and add-on devices, and centralized systems. In embodiments of the invention, a water budget percentage is determined by comparing current local geo-environmental data with stored local geo-environmental data, and the preliminary irrigation schedule or station run times are automatically modified based upon that water budget percentage. Embodiments of the present invention also provide for automation of mandated landscape watering restrictions alone, or in various combinations with water budgeting methods and apparatus.

This is a continuation of U.S. patent application Ser. No. 14/027,908filed on Sep. 16, 2013, which is a continuation of U.S. patentapplication Ser. No. 13/276,219 filed on Oct. 18, 2011, now U.S. Pat.No. 8,538,592, which is a continuation-in-part of U.S. patentapplication Ser. No. 13/159,071 filed Jun. 13, 2011, abandoned, which isa continuation in part of application Ser. No. 12/011,801 filed Jan. 30,2008, now U.S. Pat. No. 7,962,244, which is a continuation in part ofapplication Ser. No. 11/879,700 filed on Jul. 17, 2007, now U.S. Pat.No. 7,844,368, which is a continuation-in-part of U.S. Utility patentapplication Ser. No. 11/336,690 filed on Jan. 20, 2006, now U.S. Pat.No. 7,266,428, which is a continuation-in-part of U.S. Utility patentapplication Ser. No. 10/824,667 filed on Apr. 13, 2004, now U.S. Pat.No. 7,058,478, which claims the benefit of U.S. Provisional ApplicationNo. 60/465,457 filed on Apr. 25, 2003, all of which are incorporatedherein in their entirety by this reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to the management and conservation oflandscape irrigation water and more specifically, to methods andapparatus for automatically adjusting irrigation based upon changingenvironmental conditions, geographic locations and/or governmentwatering restriction regulations.

2. Description of the Prior Art

Many regions of the United States lack sufficient water resources tosatisfy all of their competing agricultural, urban, commercial andenvironmental needs. Landscape water conservation has therefore becomean important issue in the landscape irrigation industry. One reason thatlandscape water is over-utilized is that most consumers typically adjusttheir irrigation schedule an average of three times per year, ratherthan on a daily or weekly basis, regardless of changes in environmentalconditions. The relatively high cost of labor in many municipalitiesprohibits frequent manual adjustments of such irrigation controllers.This generally results in over-irrigation and runoff, particularlyduring the off-seasons, oftentimes by as much as one to two hundredpercent. Certain municipalities or water districts limit landscapeirrigation to certain times of the day, certain days of the week, orcertain days of the month. However, these require manually enteredprogramming changes several times during the course of the year,resulting in generally limited compliance and efficiency. The SouthernNevada Water Authority (SNWA) recently reported that only 7% of theircustomers were totally compliant year round. It is therefore desirableto provide methods and apparatus for automatically adjusting landscapeirrigation based upon changing environmental conditions, geographiclocations and/or government regulations.

There have been three primary approaches used to accomplish the goal ofconserving landscape irrigation water: (1) water conservation throughrestricted watering schedules (such as municipal or governmentalwatering restrictions); (2) soil moisture sensing methods; and (3)climate-based irrigation systems and methods using “smart”(self-adjusting) irrigation controllers.

Municipal watering restrictions have been used by municipalities forabout 30 years to both save water and address the water load demand onpumping and infrastructure water delivery capacities. These restrictionshave heretofore been manually entered into irrigation controllers andnormally require manual seasonal changes. The present inventor's U.S.Pat. Nos. 7,844,368 and 7,962,244 and published application No.2011/0093123, which are incorporated herein, discuss methods andapparatus for implementing municipally restricted watering schedules.These restrictions can be provided within an irrigation controller,through devices that are plugged into a controller, through devices thatare added onto a controller, or through systems for centrallybroadcasting information to remote controllers, add-ons or plug-ins.Additional embodiments for implementing restricted watering schedulesare disclosed herein.

Soil moisture sensing devices have been in available for years, but haveenjoyed only limited success. Such devices and methods generally callfor inserting moisture sensors into the soil to measure the soilmoisture content. Conventional soil moisture sensors typically breakeither the common electrical line to the valves, or break the electricalline for each individual valve. Irrometer provides such soil moisturesensors. Newer soil moisture sensing technologies have more recentlybeen developed, such as by Acclima and Baseline, and claim to be moreaccurate in measuring plant water needs. Improved soil moisturetechnology may be promising, but such devices and methods are oftenproblematic due to the location and number of sensors necessary, and thehigh costs of installing and maintaining the sensors. Nevertheless,newer and more accurate soil moisture sensing devices can provide usefuldata for use by “smart” (self-adjusting) irrigation controllers withwhich these newer sensors communicate, and related devices, includingembodiments of the present invention.

In terms of climatologically based smart controllers, a number ofirrigation controller manufacturers offer smart irrigation controllersthat calculate evapotranspiration, or “ET”, which is a representation ofthe amount of water needed by plants to replace water lost through plantabsorption and evaporation, and is expressed in inches or millimeters ofwater per day. Unfortunately, as described briefly below and in moredetail in predecessor U.S. Pat. No. 7,058,478 (which is incorporatedherein by this reference), because there are so many different methodsof calculating ET, and because so many different variables may be takeninto consideration in making ET calculations, any controller or relateddevice that actually performs ET calculations is likely to generateerroneous or unpredictable results, which is not desirable when tryingto regulate landscape irrigation.

The United States Food and Agriculture Office (USFAO), in its Irrigationand Drainage Paper No. 24, entitled “Crop Water Requirements,” notedthat “a large number of more or less empirical methods have beendeveloped over the last fifty years by numerous scientists andspecialists worldwide to estimate ET from different climatic variables.”

There are at least 15 different ET formulas. Each of these formulasprovides a different result for the reference ET (ETo). In their paperentitled “Methods to Calculate Evapotranspiration: Differences andChoices,” Diego Cattaneo and Luke Upham published a four-year analysiscomparing four different recognized ETo formulas—the Penman-Monteithformula, the Schwab formula, the Penman formula, and the Penman programdescribed in the previous patents. The comparison revealed that theresults from these four recognized formulas sometimes varied by as muchas seventy percent, particularly with the most recognizedPennman-Monteith formula discussed at length in the parent applications.(See the '478 patent col. 2, starting at line 56; and see the '428 and'368 patents, FIG. 8; and see FIG. 8 of the pending publishedapplication 2011/0093123). The following U.S. patents, among others,disclose various methods by which an irrigation controller calculates oradjusts an irrigation schedule based upon historical, distal, or localETo: 4962522; 5208855; 5479339; 5696671; and 6298285. Unlike embodimentsof the present invention, all of these inventions either calculate ETo(“reference” ET) values from weather stations or environmental sensors,or receive current service based ET data from external sources, and usesuch ET information to adjust and regulate irrigation. Several of theseexisting inventions also utilize other data, such as a precipitationsensor or a freeze sensor to shut down irrigation, respectively, duringrainy times or cold temperatures. None of these prior inventions,however, actually perform an automated water budget calculation.Conversely, embodiments of the present invention do not themselves makeany ET determinations or calculations, and do not receive or transmitcurrent ET data; however, embodiments of the present invention mayutilize or rely on historical ET data in determining the water budgetpercentage without making ET calculations within the embodiments. Suchexternal sources may be CIMIS ET databases, local sensors, cable linesor broadcast stations. Such historical ET data was used to develop FIG.1 of the parent patents and the pending published application2011/0093123.

The main objection to using ET based controllers, add-ons and plug-insis that they either calculate ET or receive ET data in order todetermine the irrigation schedule and are far too complex for theaverage user. A 2009 study sponsored by the California Department ofWater Resources (DWR) conducted by AquaCraft revealed that of the 3112ET based smart irrigation controllers used in the California study, 47%used more water than the previous conventional controllers at the samelocations during the previous year. The total resulting overall averagelandscape water saved was a disappointing 6.3%. As a consequence, manyirrigation controller manufacturers such as Toro, Irritrol, Rain Bird,and Hunter have recently gone away from calculated ET based systems andtransmitted ET based service fees, particularly for residentialapplications, in favor of much simpler and less expensive approaches.

In addition to its user unfriendliness, a second shortcoming of thecalculated ET method is its dependence upon numerous categories oflocal, real-time meteorological data and a variety of landscape specificdata such as the sprinkler precipitation rate, crop coefficient factors,type of soil, slope, degree of shade, etc. Data used for calculatingcurrent ET must be obtained by separate sensors, each one installed in aparticular location, requiring an understanding of local environmentalconditions and meteorology. Such current data must be received andprocessed in real-time, and any inaccurate, misinterpreted ormisunderstood data would result in inaccurate current ET calculations,leading to potential deviations and inefficient irrigation. HistoricalET, however, averaged over time, is less susceptible to such deviations.

Due to the urgency arising from severe national drought andenvironmental conditions, and the shortcomings of the various presenttechnologies, the irrigation industry is still, as it was in 2003,researching alternative methods for water conservation and prevention ofunattended runoff. The Center for Irrigation Technology in Fresno,Calif., along with other educational and research institutions and waterconservation agencies, is conducting studies to determine the mosteffective water conservation method. On the national level, the EPA isin the final stages of implementing a “WaterSense” irrigation efficiencyrating program similar to the “EnergyStar” rating system currently inuse for equipment energy efficiency. The purpose of such an irrigationefficiency rating program is to promote consumer awareness andcompliance as an alternative to mandated water conservation measureswhich would severely and negatively impact the irrigation industry,landscape aesthetics and the ecology. The main criteria for WaterSenselabeling is passing the SWAT test while producing at least a 20%landscape water savings, and the capability to incorporate restrictedwatering schedules. However, there is no specification or means providedfor any form of changes to automate watering restrictions during thecourse of the year, nor the ability to select from one or more set ofwatering restrictions, including the incorporation of stages of drought.

It is clear from the foregoing discussion that the landscape irrigationindustry, in view of a politically and economically sensitive, andurgent, water crisis, is pursuing highly scientific, mathematical and/ortechnical approaches for resolving the problems of wasted irrigationwater and drought conditions. Unsurprisingly, such approaches have metwith limited success in a decade of use. The EPA, United StatesDepartment of Energy (DOE), ecologists, environmentalists,municipalities, water agencies, and research institutions are allsearching for new methods that provide practical (as opposed totheoretical) irrigation efficiency—methods that overcome the particularshortcomings of the prior art.

Thus, there is an urgent need for irrigation systems that conserve waterand energy, and minimize negative impact upon the environment, byautomatically adjusting their schedules periodically in response tometeorological and seasonal changes, as well as complying with anygovernmentally-mandated watering restrictions.

The problem of irrigation mismanagement, and the main hurdle faced bythe industry, can be simply summarized as follows: once a system isproperly designed and installed, most of the wasted landscape irrigationwater and runoff is caused by failing to adjust irrigation based ondaily, periodic, or seasonal weather changes. Such inaction is usuallycaused by the complexity and difficulty of determining the particularadjustment amounts. With that in mind, correspondingly simple intuitivesolutions would be highly preferred over the existing highly theoreticaland technical, but impractical, state of the art in moisture sensing orET-based control systems.

It is therefore desirable to provide simple, user-intuitive, andtherefore readily acceptable water conservation approaches, particularlyfor clearly understood automated methods of adjusting and implementingirrigation schedules. It is further desirable to provide methods andapparatus that do not necessarily rely upon ground or air moisturesensing means, weather stations, or performing ET calculations (eitherdirectly, or as a basis for deriving watering times). It is furtherdesirable to provide methods and apparatus that minimize the margins andsources of errors by minimizing the number of sensor inputs required bythe variables in whatever formula is used. It is further desirable toprovide methods and apparatus that utilize minimal local, real-timemeteorological data. It is further desirable that such methods andapparatus be cost-efficient, affordable and usable by a large number ofpeople and entities within the different industries. It is furtherdesirable that such methods and apparatus be understandable by theaverage consumer. It is further desirable that such methods andapparatus be accomplished automatically, without requiring regularmanual adjustments by the operator of the irrigation watering timesettings or schedules. It is also desirable to provide either as analternative or in combination automated implementation of governmentalwatering restrictions along with simple automated water budget orseasonal adjust functionality.

SUMMARY OF THE INVENTION

The present invention automates the water budget or seasonal adjustfeature of irrigation controllers alone or in various combinations withautomated watering restrictions to conserve landscape water. The resultis a greatly simplified approximation of evapotranspiration methodswithout the need to calculate evapotranspiration within any of thepreferred embodiments of the present invention. The present inventionprovides numerous automated methods and apparatus for smart waterconservation and management alone or in combination with automaticimplementation of governmental or other watering restrictions incontrollers, add-ons, plug-ins, central systems or other devices.

Embodiments of the smart irrigation methods and apparatus describedherein determine or calculate a water budget percentage to be applied,for example, to a peak or summer irrigation schedule, by comparingstored to current geo-environmental data, and then apply the percentageto an irrigation schedule to adjust a controller's station start times,run times, watering intervals, or otherwise alter the controller'sirrigation schedule. In embodiments of the invention, governmental orother watering restrictions for a particular location are automaticallyselected and implemented, and automatically re-selected or updated forautomatic seasonal calendar changes. Both automatic water budgeting andautomatic implementation of restricted schedules may be provided in manyof the embodiments herein to accommodate for available water supply andinfrastructure pumping and delivery limitations for a water district,municipality, or region. In some embodiments restricted wateringschedules may be automatically implemented at some times during theyear, but not implemented at other times during the year, therebyallowing whatever smart technology is present in the controller, add-on,plug-in, or system, whether water budgeting, ET-based, soil moisturebased, or other, to adjust watering during those other times.

Various terms used in the present application are defined in advance forclarity:

-   -   1. A “smart” weather or climate based irrigation system is one        that self-adjusts its watering schedule(s) or station run        time(s) periodically to adapt to current weather conditions or        other input. The use of water budget percentages is an example        of “smart” irrigation technology. ET and soil moisture based        technologies are other examples of smart controllers.    -   2. A “conventional” irrigation controller does not have smart        technology and may also be referred to as an existing        controller.    -   3. “Seasonal adjust” is a feature available in irrigation        controllers that allows the operator to manually set or change        all of the controller station run times globally by a percentage        of the original time settings so that each individual station        run time does not have to be separately changed. It is also        convenient for the homeowner or operator to not have to remember        or record the original station run times. Usually reverting the        water budget to 100% will reset all station run times to their        original settings.    -   4. The term “water budget” or “water budget ratio” (WBR) is a        percentage of an original or preliminary watering station run        time. These terms are used numerous times in the parent patents.        The suffix “ratio” is sometimes used to clarify that this does        not refer to a budgeted volume or allotment of water. In this        context, “water budget”, “water budget ratio” and “water budget        percentage” are often used synonymously. Embodiments of the        present invention similarly automate the “seasonal adjust”        feature using a water budget ratio—without actually determining        or calculating ET—by comparing current environmental data to        stored environmental data for the controller location, hence        called geo-environmental data. Any reference to the water budget        ratio as being calculated or determined is not to be inferred as        to any specific equation, algorithm or certain variables. The        equations or algorithms used in the exemplary water budgeting        methods and apparatus of the present invention are merely        considered as one of the many methods and apparatus available,        but are not the only equations, algorithms, variables or        physical embodiments possible. An important aspect of        embodiments of the present invention is the automation of the        water budget and its use to adjust either the preliminary        station run times, start times or watering schedules (such as        watering intervals) as previously noted in the parent patents.    -   5. An “irrigation schedule” refers to a controller's programmed        schedule of start times, watering days, and/or station durations        (run times).    -   6. A “restricted irrigation schedule” refers to restricted,        allowed, or not allowed watering days of the week, days of the        month, or times of the day, as set by a governmental entity or        other authority. Embodiments of the present invention automate        such restricted schedules.    -   7. Station “run times” are part of an irrigation schedule. Hence        varying station run times is varying a specific part of varying        an irrigation schedule. Varying, modifying, or adjusting an        irrigation schedule is more general, hence broader, and may        include varying station run times, start times, watering days,        or watering intervals, or any combination thereof    -   8. “Stored” or “historical” geo-environmental data may consist        of ambient temperature, solar radiation, relative humidity,        wind, precipitation, ET, soil moisture or temperature data, or        combinations thereof. Historical or stored ET data is not        calculated or determined by or within any embodiments of the        present invention, but may be provided to, stored into, and used        by embodiments of the methods or apparatus of the present        invention.    -   9. One group of landscape water conservation methods and        apparatus of the present invention are called “temperature        budgeting” because in their simplest and preferred forms, these        embodiments only require current temperature sensor data and        some historical data to determine a water budget.    -   10. “Time of Use” (TOU) is a term used by electric utilities        starting in the early 1990's for rewarding farmers who did not        use their agricultural pumps during peak hours of the day with        significant energy rate reductions.    -   11. A distinction is made between a “plug-in” type of device,        and an “add-on” device. Both are technically add-ons because        they are both added to existing controllers, for example to make        them smart and/or to comply with watering restrictions. The        “plug-in” version of an add-on generally plugs into a controller        so that it can communicate directly with the microprocessor of        the controller. Thus, a “plug-in” can only communicate with        certain models of a host controller. A simple “add-on” is        normally attached to one or more of the outputs of a controller        to interrupt or modify or adjust such outputs according to its        programming.    -   12. SWAT (Smart Water Application Technology) is a testing        protocol for smart irrigation controllers. The EPA WaterSense        labeling program and the Irrigation Industry have accepted the        SWAT test as the standard for verifying landscape water        conservation.    -   13. A central unit or module (CM) is a unit that includes a        microprocessor that is capable of determining a water budget,        and an output to send this information to one or more remotely        located controllers, plug-ins or add-ons. The output may use a        transmitter, wireless system, internet connection, or other        dissemination device. The remote units may or may not be        independently addressable by the CM. A CM may in turn be in        communication with one or more environmental sensors by wired or        wireless means. A CM may also send (governmentally) restricted        watering schedules. A typical CM may cover a local area such as        a school, park, apartment complex, shopping center or a        cemetery; or it may broadcast to an entire neighborhood,        subdivision, city, county or other geographic region.    -   14. “Historical ET data” refers to evapotranspiration (ET) data        for a geographic location that has already been calculated        according to one or more known ET formulae. Such data may be        used by embodiments of the present invention, but no ET        calculations are actually performed by any embodiment of the        present invention.    -   15. “Non ET” means that ET is not calculated within any        embodiment of the present invention, nor is current ET received        by any embodiment of the present invention. Historical stored ET        data is not calculated within any of the embodiments, however        its use is not excluded from the preferred embodiments of the        present invention, nor its parent applications. FIG. 1 of the        '478, '428, and the '368 patent and the pending '839 application        all show the potential use of historical ET data to determine a        water budget percentage.    -   16. Watering “restrictions” are watering times of the day, days        of the week, or days of the month when landscape irrigation is        allowed or not allowed.

Embodiments of the present invention utilize one or more of thefollowing simple and effective automated implementations for landscapewater conservation: (1) automation of governmentally restricted wateringschedules; (2) automation of water budgeting within a controller, aplug-in or an add-on using periodic water budget ratios that areobtained without performing any ET calculation within the embodiments;and/or (3) automation of both governmental restrictions and waterbudgeting for maximum flexibility to accommodate local water supply andinfrastructure needs. The latter may include automatically switchingbetween smart technology (including water budgeting or any other smarttechnology) to restricted watering schedules during the course of theyear.

Automated Watering Restrictions

Municipally or governmentally mandated watering restrictions have beenaround for decades in one form or another. For example, certain odd oreven home addresses can only water during even or odd days of the month.Another example is that even addressed residences can water on Mondays,Wednesdays, and Fridays, while odd addresses can water on Tuesdays,Thursdays or Saturdays. Also, watering restrictions may limit irrigationto certain times of the day to minimize evaporation. A specific exampleof watering restrictions that is mandated by the Southern Nevada WaterAuthority (SNWA) has been discussed at length in parent U.S. Pat. Nos.7,844,368 and 7,962,244 and shown in FIGS. 6 a and 6 b herein as theSNWA (Southern Nevada Water Authority) “Drought Watering Restrictions”.However, as noted in these figures, allowed or not allowed time and dayrestrictions change several times during the course of each year toaccommodate expected seasonal conditions, thereby requiring local usersto manually reprogram their controllers to comply with these changes. Itis to be appreciated that watering restrictions are not necessarilylimited to those imposed by a municipality or governmental entity, andthat any restrictions imposed by any public or private authority arewithin the scope of embodiments of the present invention.

The following are non-limiting examples of automation of restrictedwatering schedules as provided in embodiments of the present invention:

-   -   1. A schedule of governmentally or otherwise restricted/allowed        watering times entered by the user into a controller. This        schedule may be manually entered, received over the internet,        downloaded into the irrigation controller using a USB port or a        memory stick like device, or by YFI means, or displayed on a        screen so that the user merely has to select the appropriate        restrictions without having to enter any data on the screen. The        user then enters the geographic location of the controller,        (which may be automatically determined as part of the input of        the governmental restrictions) by entry of a zip code, or the        like. In many embodiments, once the geographic location is        entered or determined, the embodiment also automatically        programs the controller for smart watering using a water        budgeting method. The controller may then be placed in        communication with at least one environmental sensor to receive        input used in performing periodic WBR calculations. The user can        then select whether he wants to do automated water budgeting,        restricted watering schedules, or a combination of both. The        programming in the controller may then prevent watering on        non-allowed days, and/or adjust watering (adjust start times or        run times) according to the according to an applicable        restricted watering schedule and/or periodically determined WBR.    -   2. Governmental or other watering restrictions may be programmed        or downloaded into a portable module, along with historical        environmental data for a geographic location. The module is then        plugged into a host controller providing it with the watering        restrictions and/or historical data for that location (such as        temperature, solar radiation, relative humidity, wind,        historical ET, etc.). Either the controller or the plug-in is        placed in communication with at least one environmental sensor        to receive input used to perform periodic WBR calculations. The        user may then select either automated watering restrictions,        automated water budgeting, or both.    -   3. Governmental or other watering restrictions could be provided        from a central unit that sends both watering restrictions and/or        the periodic (e.g. daily) water budget percentage (WBR) to local        controllers. The controllers then use the data received to        prevent watering and/or adjust their watering schedules.    -   4. Governmental or other watering restrictions are input or        downloaded into a portable module, along with historical        environmental data for a geographic location. The module is then        attached to the output of a host controller and to at least one        environmental sensor to receive input used to perform periodic        WBR calculations. The user may then select either automated        watering restrictions, automated water budgeting, or both. The        module then cuts off irrigation when not allowed according to        the governmental restrictions and/or limits irrigation according        to the WBR.

Local water authorities recognize that water conservation may beaccomplished by imposing watering restrictions, or the use of simplesmart controllers as an alternative by offering rebates and customereducation programs. Currently, without automation of either wateringrestrictions or smart technology, such authorities rely on voluntarycompliance with watering restrictions through manual adjustment ofirrigation controllers to account for daily or seasonal changes. It isexpected that automatic implementation of these restrictions throughembodiments of the present invention will be more convenient for users,will result in greater compliance, and will therefore greatly increasethe conservation of water.

One unique aspect of embodiments of the present invention is theautomation of the restricted watering schedules throughout the year, andin some embodiments this feature is combined with smart automatedtemperature budgeting or other smart technology to satisfy the recentlyproposed EPA WaterSense requirements. These automated features can beprovided through embodiments within the controller, supplied by aplug-in module, or by an add-on, with or without temperature budgetingcapability or some other ET or soil moisture based technology. The SNWArecently completed a study of 357 devices and controllers that automatedtheir watering restrictions to improve customer compliance. The resultsindicate nearly a 90% satisfaction from the users and a 13% overalllandscape water savings over a two year study period. This study wasundertaken because ET based controllers have not been effective in termsof acceptance or reported water savings.

Time of use watering restrictions are sometimes referred to as “allowed”watering times or inherently “not allowed” watering times. Automation ofwatering restrictions are provided through several embodiments of thepresent invention. Methods and apparatus for automating wateringrestrictions combined with automating water budgeting are disclosedwithin the present application in embodiments that include withoutlimitation controllers, add-ons, plug-ins and central broadcast/receiversystems.

Automatic implementations of time of use restrictions provided in theform of add-on devices are described in parent U.S. Pat. No. 7,962,244which is incorporated herein by this reference. Pending application Ser.No. 13/159,071 which is also incorporated herein by this referencediscloses automation of such restrictions within controllers. Theabstract of the '244 patent provides: “Embodiments of the invention alsoprovide methods and apparatus for updating the local wateringrestrictions and integrating the present invention into existingcontrollers.” Col. 7, lines 11-15 of the '244 patent provides: “In otherembodiments, the watering schedules of the local governmental authoritymay be incorporated with a new controller (conventional or smart)without the need for an external module to override the controller'sprogrammed watering schedules.” In addition, FIG. 8 of the '244 patentshows a new conventional or smart controller with time of useprogramming. Automatic implementation of restricted watering schedulesmay also be accomplished with a specific type of add-on called aplug-in. This device is in communication with the existing controllermicroprocessor and provides it with the restricted watering schedules tobe implemented by the controller.

Other embodiments of automated watering restrictions may be implementedinto a controller itself, as described in the '244 patent and in pendingapplication Ser. No. 13/159,071, incorporated herein. The embodiments ofthe irrigation controllers of the present invention may be provided in acommercially available device having the following components: a meansfor an operator to enter data into the controller (such as a keyboard,touch screen, dial, magnetic card readers, input port, internetconnection or remote device) and a microprocessor. In some embodiments,the input and display of the controller may be used to input one or morerestricted watering schedules. In other embodiments the restrictedwatering schedules may be downloaded into the controller add-on orplug-in. A means may be provided for selecting from multiple schedulessuch as without limitation:

-   -   1. Each restricted watering schedule may be stored within the        controller microprocessor and represented numerically. The        operator may consult his owners' manual or go to a designated        web site, enter his water district or city and enter that        numerical schedule into the controller. The controller can then        determine which internally pre-programmed schedule to access and        implement.    -   2. Restricted watering schedules may be developed by accessing        an internet site where the allowed watering days, times of day,        seasonal changes, drought stages, even or odd street addresses,        or watering groups may be programmed onto the computer screen        and downloaded directly or through a portable device such as a        flash memory stick or the like, and entered into the controller,        add-on or plug-in. (See FIG. 15) In some embodiments of the        invention, restricted watering schedules may be sent from a        central location to remote controllers, add-ons or plug-ins        either wirelessly or via the internet. During the course of        irrigation during the year, the controller only allows        irrigation to occur during the allowed watering times of the        day, day or the week, day of the month, etc.

Other embodiments implementing restricted watering schedules areprovided by a central system, which may be local, city wide, countywide, etc. Each controller may be given an address which the centralsystem uses to send the automated restricted watering schedules to suchcontrollers. Certain controllers, for example, are addressed to water oncertain days of the week, or certain times of the day, or certain daysof the month. Other controllers are addressed to water on other days ofthe week, or at other times, etc. In related embodiments, seasonalchanges in watering restrictions are also automatically implemented,and/or water budgeting may also be automatically implemented.

Automated Seasonal Adjust or Water Budgeting.

As first set forth in parent U.S. Pat. No. 7,058,478 (col. 7, lines31-38) and subsequent patents and pending applications, preferredmethods and apparatus for water budgeting rely on the followinguniversally understood concepts: (1) more water is required to irrigatelandscape or crops during periods of warmer temperatures; (2) less wateris required during periods of cooler temperatures; (3) little or nowater is required or desired below a certain temperature, or duringcertain times of the year; (4) little or no irrigation water is requiredwhile it is raining or cold, and for a period thereafter.

In embodiments that use temperature budgeting within an irrigationcontroller, the operator first attaches the controller to an irrigationsystem. This can be done at any time of the year, not merely during thesummer months. In an example of preferred and simple embodiments ofmethods and apparatus, the user installs a temperature sensor or one ormore additional sensors within the target geographical area, andinitiates its communication between the sensor(s) and the controller.For example, an optional readily available rain sensor may also beinstalled, and placed in communication with the controller. The userthen programs an exemplary controller with an irrigation schedule(preferably the summer or peak schedule) using personal experience,professional assistance, with internet provided guidelines, or by othermeans.

If not already present, the time and date are entered into the exemplarycontroller. Then, the physical location of the controller is entered,for example by providing the local zip code. This compares to the morecomplicated need to provide ET based controllers with information suchas precipitation rates, soil type, slope, crop coefficient factors,system efficiency, and degree of shade or sun to calculate thepreliminary irrigation schedule, and multiple sensors or a weatherstation, or a monthly service fee for ET data. The preferred temperaturebudgeting methods and apparatus of the present invention do not use anyform of ET, while other embodiments discussed more fully below may usehistorical ET.

Once the zip code or other geographic location information is entered inthese exemplary temperature budgeting embodiments, in preferredembodiments, the controller then automatically determines theextraterrestrial radiation factor (RA) for the standard date andlocation from a look-up table stored within the controller. The RAutilized by this invention must be distinguished from the solarradiation value (Rn or Rs) provided by weather stations and sensors, andutilized by ETo formulas. Specifically, RA is a function of the angle atwhich the sun strikes the earth at various times of the year at variouslatitudes, expressed as virtual evaporation in units of milliliters ofwater (the same units of measurement as ET) while solar radiation is ameasure of the actual intensity of sunlight at a particular time. Inother embodiments, the controller may look up other historicalenvironmental data, such as historical ET, and use it in a way that issimilar to the way RA is used.

It is to be appreciated that a primary object of water budgeting is toobtain a ratio or percentage by which a controller watering schedule maybe adjusted. Thus, any suitable determination or set of calculationsthat results in such a ratio is within the scope of the presentinvention. By way of example, and without limitation, in thistemperature budgeting example, the controller first automaticallycalculates a standard temperature budget factor (STBF) using dataprovided by the operator (e.g., the July average summer hightemperature, and the latitude; or by the use of a zip code or otherlocation identifier that identifies the latitude and historical averagesummer high temperature), and using any number of relatively simpleformulas utilizing this data. As described in greater detail in theparent patents, one method of calculating the STBF is to multiply thehigh summer temperature (either provided by the operator or by theentered zip code) by an RA (the RA determined by the particulargeographic location of the controller, and either the estimated date ofthe summer high temperature or the average summer RA values for theparticular geographic location). The STBF is then stored for subsequentuse in determining the water budget ratio (WBR) percentage. It is to beappreciated that no ET calculation is performed here, although in otherembodiments, historical ET data may be used instead of RA data.

In this non-limiting example, the controller may also obtain the actualhigh temperature and RA for the particular current period, the formerfrom a temperature sensor and the latter from an internal look-up tableor other suitable source. Such periodic (current) data is used tocalculate the periodic temperature budget factor (PTBF). The PTBF shouldbe calculated utilizing the same formula for calculating the STBF, butusing currently available data rather than the data initially providedby the operator. The controller then computes the WBR by dividing thePTBF by the STBF. This ratio is then used to adjust the preliminaryirrigation schedule or run times for that particular period. It is to beappreciated that variations on these calculations of STBF and PTBF arewithin the scope of the present invention, and/or other or differentcalculations may be performed to obtain the desired water budget ratio(percentage). It is also to be appreciated that no ET calculation isperformed in developing the water budget ratio.

Once the WBR has been determined, the preliminary irrigation schedulemay be multiplied by the WBR to obtain the modified (actual) irrigationschedule. The controller then irrigates the irrigation area pursuant tothe modified irrigation schedule, as described in greater detail herein(e.g., changing station run times and/or start times and/or schedules).It is to be appreciated that these particular examples of temperaturebudgeting embodiments of the invention do not require, use or calculateany form of ET information. However, other embodiments of the presentinvention may use other historical data, including historical ET data,without calculating ET within the embodiments of the present invention,to determine the water budget percentage. The present invention is notto be limited by any particular equation, nor any variables used withinany equation in determining the water budget or water budget ratio

It is to be appreciated that temperature budgeting may also beimplemented in other embodiments of the present invention includingwithout limitation add-ons, plug-ins, central (broadcasting) systems,and/or other similar systems.

Because embodiments of the present invention relationally adjust anirrigation schedule, they are suitable for nearly all conditions andlocations. Embodiments of the present invention can compensate fornumerous characteristics and specifications of an existing irrigationsystem, and unlike prior systems, these embodiments do not requiremultiple complicated formulas or variables. Embodiments of the presentinvention can also inherently compensate for particular environmentalconditions. For example, they may be applied to the “cycle and soak”method commonly utilized for sloped landscapes, since they increase ordecrease the initial irrigation schedule for the sloped landscape basedupon the WBR.

It is once again to be appreciated that the specific algorithm andparameters used in determining the WBR while performing temperaturebudgeting represent only some embodiments of the invention. Otheralgorithms, equations, or parameters may be used to calculate the WBR,as described more fully elsewhere herein, and the appended claims arenot to be limited to any examples of calculating a water budgetpercentage.

The present methods and apparatus for adjusting an irrigation schedulemay be used year-round, and at any geographic location. For example, inthe northern hemisphere, the winter PTBF will typically be much lowerthan the STBF, resulting in a much lower WBR value. This in turnsignificantly decreases the irrigation duration, which is consistentwith the average consumer's understanding that irrigation is not asnecessary during the winter months. When the operator inputs a minimumtemperature and utilizes the precipitation sensor, embodiments of thepresent invention are able to completely cease irrigation duringunnecessary periods.

Alternative embodiments of an apparatus of the present invention providean add-on temperature budgeting or alternate automated water budgetingmodule. This add-on module is placed along the output path of anexisting irrigation controller, so that it intercepts and processes anysignals from the controller to the irrigation system. This moduledetermines the WBR in the same way(s) as in the above-describedirrigation controller embodiments, and permits the operator to add thefeatures and functions of the present invention described herein to anyexisting irrigation controller without replacing the old controllerentirely.

Other embodiments of an apparatus of the present invention areimplemented using a plug-in module provided with environmental sensordata. The plug-in is also provided with historical data for the selectedgeographic region. The plug-in then periodically (preferably daily)calculates a water budget ratio using the methodology describedelsewhere herein. A microprocessor in the plug-in module thencommunicates this periodic (e.g., daily) water budget to the controllermicroprocessor which can easily access its existing watering schedulesand adjust the summer or preliminary irrigation schedule station runtimes accordingly. This communication with the host controller can behard wired or wireless. The environmental sensor(s) can be as simple asa temperature sensor, or a combination of sensors such as withoutlimitation solar radiation, wind, soil moisture, relative humidity, andtemperature.

Power for the various embodiments described herein may be from AC power,from a solar panel, batteries, or ambient light.

Optional features may also be incorporated into embodiments of thepresent invention. For example, the operator may specify a minimumirrigation temperature. This insures that the irrigation schedule is notactivated when the temperature is near or below a certain point, such asfreezing temperature. Such a minimum temperature requirement serves twoprimary purposes—first, to conserve water, and second, to protect thesafety of vehicles and pedestrians traveling through the irrigation zoneduring freezing temperatures. A second optional feature permits theoperator to further adjust the irrigation schedule according to theparticular circumstances and/or limitations, such as the water deliverymethod utilized by the irrigation system, the specifications of thesystem, or the type of plants being watered. This allows the operator tofine-tune the irrigation schedule based upon personal experience,observations or unusual field situations. A third optional feature is toprovide a commonly available precipitation sensor in communication withthe embodiment of the invention, either directly or indirectly as aseparate unit (e.g., through a physical hard-wired connection, awireless connection or radio transmission; or as a component built intoan irrigation controller), so that the embodiment may detect, forexample, the occurrence of rainfall and suppress the irrigation scheduleduring the affected periods. The particular effect of current or recentprecipitation upon the irrigation schedule may be determined by theoperator. For example, the operator may cause the embodiment to suppressthe irrigation schedule if precipitation occurred within the previoustwenty-four hours, or only if precipitation is occurring at theparticular moment of irrigation. Additionally, direct input into thecontroller, plug-in or add-on microprocessor may allow for adjustment ofthe irrigation delay period depending upon the amount of rainfall or theintensity of rainfall. A hygroscopic rain switch or a “tipping bucket”type of rain sensor may be provided by wired or wireless means inaddition to one or more environmental sensors. The rain delay irrigationshutdown may be adjustable within the controller, add-on or plug-independing upon the duration of the rainfall, amount of precipitation, orintensity of the precipitation.

As an alternative to water budgeting based on temperature sensorinformation, other methods and apparatus contemplated by the presentinvention to conserve landscape irrigation water may utilize soilmoisture sensors to automate the water budget feature. Soil moisturesensors that merely break the line to one or more valves are not withinscope of the present invention. However, newer soil moisture sensors maybe used instead of (or in combination with) temperature or otherenvironmental sensors in embodiments of the present invention to providedata used to calculate WBR and adjust the station run times orirrigation schedules. As with other embodiments, a water budgetpercentage is determined in these embodiments by comparing currentgeo-environmental data (e.g., data received from a soil sensor) tostored geo-environmental data without determining or calculating ET.

For example, assuming that soil moisture sensors are installed remotelyin a landscaped area, these sensors could provide data such as soiltemperature or soil moisture data from a certain location. This data iscurrent or real time geo-environmental data. Historic data consisting ofsoil moisture and soil temperature data is stored within the controller.A minimum and maximum root zone watering threshold is established withinthe controller microprocessor. When the historic geo-environmental datais compared to current geo-environmental data, a percentage of thepreviously set station watering run time may be required to replenishthe root zone for that location to reach the maximum threshold level.

It is therefore an objective of the present invention to provide simpleand straightforward methods and apparatus for irrigation waterconservation, that are naturally intuitive such that they may be used bya wide variety of people or entities in different circumstancesencompassing automated implementation of water budgeting and automatedimplementation of governmentally restricted watering schedules.

It is another objective of the present invention to offer a choice ofautomated smart water budgeting or automated watering restrictions, orboth, with the additional ability to select from one or more suchautomated restricted schedules.

It is another objective of the present invention to provide methods andapparatus for conserving water by automatically adjusting irrigationschedules in response to varying climatic conditions.

It is another objective of the present invention to provide a methodsand apparatus that utilize greatly simplified local, real-timemeteorological data to make calculations used to adjust irrigationschedules.

It is another objective of the present invention to provide methods andapparatus that minimize the margins and sources of error withinautomatically and climatically adjusted irrigation schedules by limitingthe number of variables and relationships necessary to calculate andadjust the schedules.

It is another objective of the present invention to provide methods andapparatus that may be embodied into any irrigation controller that areinexpensive to manufacture, install, operate and maintain.

It is another objective of the present invention to provide automatedmethods and apparatus for water conservation and management andimplementation of governmental or other watering restrictions.

Additional objects of the present invention shall be apparent from thedetailed description and claims herein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is an analytical comparison of evapotranspiration (ET) andtemperature budget percentage values for certain geographical areas ofCalifornia over a five year period, beginning in 1997. This comparisonis also shown as FIG. 1 in parent U.S. Pat. Nos. 7,058,478; 7,266,428;7,844,368 and of published pending application Ser. No. 12/955,839 fromwhich this application claims priority.

FIG. 1B shows a variety of ET-based historic bell curves for variouslocations identified by zip codes.

FIG. 2 shows the published extraterrestrial radiation factor chart forvarious latitudes. This chart is also shown as FIG. 6 in parent U.S.Pat. Nos. 7,058,478; 7,266,428; 7,844,368; and of published pendingapplication Ser. No. 12/955,839 from which this application claimspriority.

FIG. 3 illustrates a block diagram of an embodiment of a smartirrigation controller. This diagram is very similar to FIG. 2 in parentU.S. Pat. Nos. 7,058,478; 7,266,428; and 7,844,368 from which thisapplication claims priority.

FIG. 4 is a flow chart of an embodiment of a preferred method oftemperature budgeting within the controller of FIG. 3. A similar diagramis also shown as FIG. 4 in parent U.S. Pat. Nos. 7,266,428 and 7,844,368from which this application claims priority.

FIGS. 5A, 5B, and 5C show the SWAT results of two controllers and oneadd-on device using temperature budgeting.

FIGS. 6A and 6B show an example of seasonally restricted wateringschedule as specified by the SNWA.

FIG. 7 shows the block diagram of an embodiment of an add-on to anexisting controller to make it smart or to enforce compliance withrestricted watering schedules. This embodiment is also shown in FIG. 19Cof the U.S. Pat. No. 7,844,368.

FIG. 8 is a block diagram of an embodiment of a plug-in to an existingcontroller to make it smart or enforce compliance with restrictedwatering schedules.

FIGS. 9A, 9B, and 9C are block diagrams of embodiments of a centralbroadcasting system that may provide a water budget percentage and/orrestricted watering schedules to remote irrigation controllers, plug-insor add-ons.

FIG. 10A is a flow chart of a smart or conventional controller used withan embodiment of an add-on with automated seasonal wateringrestrictions.

FIG. 10B is a flow chart of a smart or conventional controller used withan embodiment of a plug-in with automated seasonal wateringrestrictions.

FIG. 11A is a flow chart of a conventional controller in communicationwith an add-on embodiment of the present invention that is capable ofcontrolling dual use of watering restrictions and smart technology inthe add-on.

FIG. 11B is a flow chart of a smart controller embodiment of the presentinvention that is capable of controlling dual use of wateringrestrictions and smart technology that may be ET based or water budgetpercentage based.

FIG. 12 is an exemplary flow chart depicting alternate implementationsusing water budgets including adjusting station run times daily, theaccumulation method, and the adjustment of watering intervals, aspreviously depicted in FIG. 4A of U.S. Pat. No. 7,844,368.

FIGS. 13A and 13B show two embodiments of an add-on that learns thecontroller station run times and modifies the outputs of the controlleraccordingly.

FIG. 14 illustrates an embodiment of a self-contained irrigationcontroller in an outdoor pedestal showing internal temperature and rainsensors.

FIG. 15 is an example of a computer screen that may be used to select,program, and implement automated watering restrictions, includingalternating between smart use and restricted watering use.

DETAILED DESCRIPTION

Referring to the drawings wherein like reference characters designatelike or corresponding parts throughout the several views, and referringparticularly to the chart of FIG. 1, it is seen that this chart comparesthe monthly ET percentage values obtained using the Penman-Monteithformula (currently favored by the USFAO and CIMIS) with the ratios(percentages) obtained utilizing a temperature budgeting formula of apreferred embodiment described herein. Such comparison was made over aperiod of five years at twenty-five environmentally-diverse locationswithin the State of California. Both formulas used the same CIMIS data.For the Penman-Monteith formula, the published historical monthly ETowas divided by the historical summer ETo. The monthly temperature budgetfactors obtained by the present invention were similarly divided by thesummer temperature factor. The ETo ratio is then compared to the WBR forrelative accuracy. As indicated by FIG. 1, the values obtained using aformula of an embodiment of the present invention closely approximatethe Penman-Monteith, generally more so than the other ET formulas suchas those referenced in the Catteano and Upham study. This indicates thatthe temperature budgeting embodiments of the present invention arecomparable to the other ET formulas, since a simple to understand methodof the present invention is ninety-five percent as accurate or betterthan a more complicated ET calculation.

FIG. 1A also illustrates that historical ET percentage calculationsclosely approximate temperature budgeting percentage calculations ofembodiments of the present invention, demonstrating that historical ETmay be reliably used in determining water budget ratios in embodimentsof the present invention. In particular, and without limitation,historical ET may be used in a manner similar to the STBF, and/orhistorical ET may be used in calculating the STBF, and/or historical ETmay be used in calculating the WBR. It is not necessary, nor is it partof any embodiment of the present invention, to actually performcalculations resulting in ET values; instead, it is to be appreciatedthat previously-calculated historic ET values may be used in someembodiments of the present invention.

Furthermore, the present invention is advantageous over thePenman-Monteith, or any other ET, formula in that it reaches similarirrigation time values or irrigation schedules without relying upon thenumerous variables and relationships of ET theory, or a subsequentcalculation of irrigation time settings as described in the parentapplications.

Another advantage of the present invention over the Penman-Monteithformula, or any other ET formula, is in terms of hardware costs.Specifically, in at least one alternative embodiment, the only newhardware required is a temperature sensor—an existing irrigationcontroller, assuming that it satisfies certain minimum systemrequirements (such as the availability of an input port for thetemperature sensor, sufficient memory to store the RA lookup table, andthe ability to receive the software instructions for the presentinvention), may otherwise be used. This controller may be AC, DC, solar,or battery-powered.

FIG. 1B shows historical percentage (WBR) curves for various zip codeselected locations in the U.S. As expected, Hawaii has the flattest WBRbell curve because of its year round relatively low range of hightemperatures.

FIG. 2 is a published (prior art) listing of extraterrestrial radiationexpressed in equivalent evaporation. This Ra chart is used with one ofthe preferred embodiments that does not require the use of historicalET. Alternative embodiments may use historical ET instead of Ra becausehistorical ET is as simple to implement in the determination of thewater budget ratio. When historical ET is used, it can effectively besubstituted for the Ra factor because both the Ra and ET use the sameunits of measurement, which are millimeters of water per day. In bothcases, a percentage or ratio is determined by comparing stored tocurrent geo-environmental data.

FIG. 3 is a block diagram of a typical irrigation controller with one ormore external environmental sensors, an optional external precipitationsensor, a microprocessor with data storage, and a power supply. Theexternal temperature, soil, solar radiation, wind, relative humidity orother sensors are provided by wired or wireless means as current or realtime sensor data. These sensors are in communication with the controller

FIG. 4 shows a flow diagram for the exemplary controller of FIG. 3 whichis depicted as a smart controller using an embodiment of temperaturebudgeting. In this non-limiting example, the operator installs theirrigation controller and connects it to one or more irrigation valves(step 30). The temperature sensor or any other sensor (rain, wind, solarradiation, soil moisture, soil temperature, relative humidity orcombinations thereof) are placed in communication with the controllermicroprocessor by wired or wireless means (32 and 33). The operatorconfigures the irrigation controller (e.g., programs the summer or peakirrigation schedule) by first entering the date and time (41). Inpreferred embodiments, the operator then enters the local zip code (43b) which may automatically provide latitude, the Ra factors, and thehistoric temperature data, or alternately historic July or peak ET dataas shown in item 43 c, or monthly, weekly, or daily alternate historicand stored geo-environmental data (item 43 d).

In step 44 of FIG. 4, the operator enters the preliminary (e.g., summer)irrigation schedule from personal experience, professional assistance,or with internet or other guidance. If a minimum irrigation temperatureis desired, that is entered in step 45. The microprocessor thendetermines the water budget ratio or percentage (71 b) and adjusts thepreliminary irrigation schedule according to the determined water budgetratio. Additional sensors (71 a) may be used to determine whether or notto stop irrigation (81, 82) based on recent precipitation, rain, etc.The controller then activates the valves with station run times modifiedor adjusted according to the water budget ratio if the minimumirrigation temperature is exceeded and there is no precipitation. Asimilar water budget determination may be made using historic average ETcompared to historic monthly ET, and adjusted according to the currenttemperature compared to the expected historic temperature for that day.

As with the other embodiments, multiple watering restrictions could beprogrammed within the controller and selected by zip code, region,municipality, or water district designation. These restrictions may thenbe varied automatically by embodiments of the invention at various timesof the year, but typically seasonally (but not necessarily based uponthe calendar seasons) because of the wide diversity of the locationssuch as dry deserts, the humid South East, the coast, mountains,northern colder states, etc. In particular, automatic implementation ofwatering restrictions may be used in conjunction with automaticimplementation water budgeting in numerous embodiments of the presentinvention. In some of those embodiments, watering is prevented accordingto an applicable restricted schedule and then, when allowed, watering islimited (the controller's watering schedule is modified) by a waterbudget ratio. In other embodiments, watering start times or wateringdays are moved to comply with the applicable watering restrictions, andwatering is then limited by a water budget ratio. In other embodiments,during some times of the year, watering may be prevented or start timesmoved (as above) according to the applicable watering restrictionswithout any watering limitations when watering is allowed; but duringother times of the year, the watering restrictions are not used, andwatering is instead limited according to whatever “smart” irrigationtechnology is in place, which may or may not use water budget ratios.

FIGS. 5A, 5B, 5C show the results of three products that use preferredtemperature budgeting tested under the SWAT protocol. FIG. 5 a is forthe Smart Clock and shows an average deviation of 0.2% from thePennman-Monteith standard landscape evapotranspiration root zone watercontent. FIG. 5B is for a battery powered smart controller with a selfcontained temperature sensor which shows an average deviation of 1% fromthe standard root zone ET based watering needs. FIG. 5C is for theUniversal Smart Module, an add-on device that determines water budgetingand modifies the output of any AC powered controller based on that waterbudget percentage. In all three products, virtually no irrigationdeficit was noted. These results confirm the analytical study of FIG. 1Athat the water budget determination method closely approximates ETwithout its complications.

FIGS. 6A and 6B are the “Drought Watering Restrictions” imposed by theSouthern Nevada Water Authority (SNWA). The entire area of SouthernNevada is divided into six landscape water zones A-F. Each zone canwater on different days, which vary depending upon the season. Inaddition, depending upon the season, only certain times of the day areallowed watering times. For example in FIG. 6A, watering group B canwater Tuesdays, Thursdays and Saturdays during the spring or fall, butonly on Tuesdays in the winter. During the summer, all groups may waterevery day, but irrigation is prohibited as noted in FIG. 6 b during thesummer between 11 am and 7 pm. The SNWA seasons are defined as March 1to April 30 for spring, May 1 to August 31 for summer, September 1 toOctober 31 for fall, and November 1 to the end of February for winter.Note that these seasonal changes to not match calendar seasons.

As heretofore prescribed, the operator would need to manually modify thecontroller watering days or times of the day to comply with theseseasonal requirements. This fact is the main reason why total compliancein the SNWA region was only 8% historically and resulted in many finesfor those who did not change their schedules manually by seasons.

FIG. 7 shows an embodiment of an add-on device or module attached to thecommon electrical line from the controller to one or more valves. Thecontroller which may be smart or conventional is programmed with itssummer or peak irrigation schedule, including its station run times. Thepreliminary schedule can be determined by any means available such asfrom personal experience, web site assistance, with or without the useof historical data which may include stored ET data, or by professionalassistance.

The cutoff switch is internal to this embodiment of an add-on and breaksthe common line to inhibit irrigation when watering is not allowed. Inaddition, or alternatively, this or other add-on devices can also beprogrammed to make the existing irrigation controller smart either bylearning the summer or peak watering run times and modifying them duringother times of the year, or accumulating the daily water budgets until athreshold is reached and then allow the existing controller to irrigateits summer schedule. The result of accumulation would be to increase thewatering interval of days during the cooler times of the year. Thus,this exemplary add-on can be a time of use restricted wateringscheduler, a water budget determinator for daily station run timeadjustments, or a watering schedule changer if used in the accumulationmode, or any combination thereof. In many of these applications, thewiring is identical as shown in FIG. 7.

For example, if the controller is located in the SNWA area, the locationmay be designated as watering group “B” as shown in FIG. 6A. Withoutregard to the watering restrictions, the controller is programmed tostart an irrigation cycle every day. The start time is set for 7:00 am,and the station run times are set for a summer schedule having aduration of 8 minutes for a particular station. If the current date isSep. 16, 2011, the programming of this exemplary module as a TOU unitcould be:

Entering the date and time as Sep. 16, 2011 and 4:00 pm.

The watering group is entered as “B” during the course of programmingthe module. According to the 2011 calendar, September 16 is a Friday.According to the SNWA (FIG. 6A), Group B can only water on Tuesdays,Thursdays, and Saturdays. Therefore, group B is not allowed to water onFriday September 16. In this case, a cutoff switch in the module, suchas that shown in FIG. 7 is open all day starting at midnight, and doesnot allow irrigation to occur at 7 am or at any other time during thatday when the controller attempts to irrigate.

Now let us assume that the exemplary add-on is an embodiment that worksas an accumulation smart add-on. In this case, the controller is stillprogrammed with its summer irrigation schedule with start times,watering days, and station durations (run times). The module isconnected to the output in the same way as the TOU device. In this case,however, one or more sensors (122) are provided to the module whichcommunicates environmental data to the module microprocessor. Thesesensors could be temperature, rain, solar radiation, wind, relativehumidity or any combination thereof. Location information (such as thezip code) is entered and the microprocessor selects from its internaldata storage of historical environmental data for that location. Suchdata may once again be temperature, solar radiation, wind relativehumidity, soil moisture, soil temperature, historic ET data, etc.Periodically, (preferably once a day at midnight), the microprocessordetermines the water budget ratio (percentage) by comparing storedgeo-environmental data to current geo-environmental data from the sensor(such as today's high temperature). For this exemplary accumulationembodiment, a minimum threshold level is entered or established. Themodule will not allow irrigation until that threshold is met orexceeded. This threshold may be defined by the user, and could beanywhere up to 100% (depending on such things as soil and landscapevegetation type, to insure that an adequate amount irrigation run timeis provided to allow for deep root penetration. Water budget percentagesare calculated each day, and accumulated day after day until thethreshold is reached. On the day (or day after) the threshold isreached, watering is then allowed to occur. For example, if it is duringthe cooler time of the year, such as December in the NorthernHemisphere, the daily accumulation may only be 14% for the first day,and perhaps 16% the next day, and so on. If the threshold is set for100%, at this rate it may take six days before irrigation is allowed.

In related embodiments, if automatic time of use restrictions are alsoincorporated into the module, and the threshold is reached on anon-watering day, irrigation is prevented until an allowed day isreached. This procedure is very similar to the accumulation method ofFIG. 12, except that this is done in an add-on instead of within acontroller.

Some advantages of this type of add-on are:

-   -   1. The module is compatible with any module or size of AC        powered irrigation controllers. It is even compatible with a DC        powered controller with a minor change to the hardware (such as        that shown in FIG. 19B of the '368 patent).    -   2. Since the module will work with any controller, the operator        (homeowner, landscape maintenance contractor, apartment manager,        etc.) keeps his existing controller that he is familiar with.    -   3. The cost of the add-on is less than a new smart controller.    -   4. Only one model of module needs to be inventoried or learned        for universal use.    -   5. The module can make any existing controller smart or make any        existing controller, smart or conventional, comply with watering        restrictions.    -   6. The module will save more water because of its simplicity and        increased use and compliance.

FIG. 8 shows an embodiment of a smart plug-in of a time of use wateringrestriction device in direct communication with an existing controllermicroprocessor. In this case, the plug-in is still an add-on in that itis added to an existing controller to make it smart, but this type ofmodule can communicate with the controller's microprocessor. Thisexemplary plug-in module may be provided with one or more environmentalsensors, and possibly a rain sensor. The plug-in has internal historicgeo-environmental data which may consist of ambient or soil temperature,solar radiation, wind, relative humidity, or historical ET for thatlocation. In addition, it may perform a daily water budget or seasonaladjust determination which is then communicated to the controllerdirectly. The existing controller then adjusts its station run timesaccordingly if the daily water budget method is used. If accumulation isused, the plug-in or controller is programmed with the desired thresholdand the controller initiates irrigation when the threshold is reached orexceeded.

In addition to smart technology, watering restrictions could be enteredinto the plug-in or downloaded into it through the internet, by wirelessmeans, by means of a small data storage device loaded with one or morewatering restriction schedules, or by other means. Entering the zip codeor a numbered location may allow the module to select the specificmunicipal watering restrictions appropriate to that location. A WI-FIcommunication link could also provide this allowed/not allowed wateringdata. Power for the plug-in could be provided from the controller, orthe plug-in could be battery powered. Once again, the environmentalsensor data could be provided by wired or wireless means.

Again, the specific equation or parameters or types and combinations ofsensors, or whether they are wired or wireless does not alter the smartinvention, which is to alter the watering schedule of a controller bydetermining a water budget percentage by comparing current to historicalgeo-environmental data, and use that water budget to vary the stationrun times or adjust the irrigation schedule.

In terms of restricted watering schedules, the preferred method of thisinvention is to provide one or more restricted watering schedules,select the appropriate one if more than one is provided, and modify thecontroller irrigation to match the allowed watering days of the week,days of the month, or the times of the day, to include the seasonalautomation of those schedules. This may be done by simply preventingirrigation on days/times when not allowed according to the applicablerestricted schedule, or by modifying station start times so thatirrigation occurs on dates or times when allowed according to theschedule. In related embodiments that also include water budgeting, oncean allowed watering time (or start time) is reached, the watering may belimited (e.g., shorten station run times) according to the water budgetpercentage.

FIG. 9A shows a block diagram of an embodiment of a centralized system.Such a central unit may be designed to cover a park, school, apartmentcomplex, or the like, sending the water budget or watering restrictions,or both, to remotely located controllers such as in FIG. 9A, or to aplug-in of FIG. 9B, or to an add-on of FIG. 9C. Such remotely locatedunits may be addressed as a single group, multiple groups, orindividually by the central unit. Normally, the communication is bywireless means (broadcast), although the central unit may communicate tothe controllers, add-ons or plug-ins over the internet, or by othersuitable means. Alternately, the central system may consist of a citywide central irrigation system sending to all three embodiments. As inthe other embodiments, the water budget percentage and/or automatedwatering restrictions can be sent.

It is to be appreciated that the various steps and parts of the methodsand apparatus of the present invention may be distributed in differentpermutations and combinations between the central unit and the receivingunits (controllers, add-ons or plug-ins). For example, and withoutlimitation, in some embodiments, the central unit may generate the waterbudget percentages and send them to the receiving units forimplementation. In other embodiments, the central unit may simplyprovide current environmental data to the receiving units whichthemselves generate and then implement the water budget percentages. Inother embodiments, the central unit may receive several sets of wateringrestrictions (e.g., different restrictions being applicable at differentseasons of the year), and the central unit decides which restrictionsare currently in effect and sends those to the receiving units; in otherembodiments the central unit sends all of the restriction sets to thereceiving units which themselves determine which one is currentlyapplicable. In some embodiments, water budget percentages may beaccumulated in the central unit; in other embodiments, those percentagesmay be accumulated in the receiving units. In very simple embodiments,the central unit may perform numerous functions and simply send a “ok towater” or “not ok to water” signal (or a “start watering”/“stopwatering” signal) to the receiving units. The central unit may alsoseparately address individual receiving units. It is to be appreciatedthat these are only examples of how the steps and apparatus ofembodiments of the present invention may be divided up between thecentral unit and the receiving units.

FIG. 10A is a flow chart of an embodiment of an add-on used with a smartor conventional controller, with TOU restrictions in the add-on. Thecontroller may be programmed either conventionally or with the smarttechnology of choice, which may be with a temperature budgeting methodof the present invention, or some other smart technology such asinternal ET calculations or provided with ET data. The add-on embodimentis attached to an output of the controller to allow it to break thecommon line with its cut off switch such as that shown in FIG. 7. Theadd-on is programmed with historical geo-environmental data fromlocation information (such as a zip code or latitude and longitude, orby environmental region). The programming of the add-on can be donemanually, over the internet, or from a computer from which a memorydevice can transfer such historic data.

In addition, multiple restricted watering schedules may bepre-programmed into the exemplary add-on from which the restricted (TOU)schedule may be selected based on entering a zip code or other locationdata. The selected restricted schedule also provides the seasonalchanges mandated by that municipality or water district. The add-on willthen automate the changes to the allowed watering times of day, days ofthe week, or days of the month.

In some embodiments, once the smart or conventional controllerdetermines it is time to irrigate, 24 VAC (or pulsed 12 VDC) is appliedto the valves to energize in an attempt to irrigate. If it is not anallowed watering day or time of day, the cutoff switch is open. On anallowed watering day, the cutoff switch is closed, allowing irrigationto occur.

For DC applications, a diode may be placed in the circuit as shown inFIG. 19B of the '368 patent which is biased to only allow the closing ofa valve and does not allow opening when the cutoff switch contact isopen.

Referring to FIG. 10B, the controller may again be smart orconventional. In this exemplary embodiment, a plug-in is literallyplugged into the controller to communicate with its microprocessor.Plug-ins can only communicate with compatible models of controllers andare therefore not universal, whereas an add-on that breaks the commonline is compatible with virtually any controller. The plug-in isprovided with or pre-programmed with one or more restricted wateringschedules. Entering a location identifier (such as a zip code) selectsthe restricted schedule appropriate for that location. Entering date andtime allows an applicable one of several schedules to be selected. Therestricted schedule will often contain seasonal variations to itsrestricted watering schedule as noted in the SNWA FIGS. 6A and 6B.

Once the plug-in is programmed, it communicates the selected restrictedwatering schedule to the controller. The plug-in in effect becomes agovernor of the irrigation controller. If the controller is smart, itmay withhold activating the valves until an allowed watering day or timeof day arrives; if not, the plug-in itself may prevent irrigation untilsuch time.

FIG. 11A demonstrates the dual use of smart technology and wateringrestriction schedules, not at the same time, but during certain periodsof the year. A conventional (e.g. not “smart”) controller is programmedwith an irrigation schedule appropriate to the landscape, and isprovided with one or more irrigation shut down sensors. An add-on isattached to its output(s) which has a microprocessor that communicateswith one or more environmental sensors, and has been provided with waterrestrictions programming. An output cutoff switch is provided within themodule to allow irrigation when the switch is closed. The microprocessorin the add-on also has a calendar which can be programmed with datesduring which smart technology is to be implemented, and other dates whenrestricted schedules are to be implemented.

In the exemplary dual use embodiment of FIG. 11A, if the calendarindicates that restricted watering schedules are appropriate for thatday or period during the year, the add-on microprocessor uses theapplicable restricted watering schedule to determine if it is an allowedwatering day. If not, the switch contact within the add-on stays open(preventing irrigation) and the microprocessor waits until an allowedwatering time of day, day of the week, or day of the month arrivesbefore closing the contact. During the allowed watering time, the switchcontact closes, allowing the controller to irrigate according to itsirrigation schedule.

However, in this exemplary embodiment, the calendar may indicate thatinstead of restricted watering schedules, smart technology is to beimplemented, which can be real-time ET-based, historical ET-based, waterbudget based, ground moisture sensor based, etc. The flow chart of FIG.11A illustrates the use of smart technology that is water budget based.The two methods of water budgeting are daily water budgeting, whichallows a percentage of the summer station run times typically on a dailybasis, or the accumulation method. If the daily water budget is used,the add-on may have learned the summer run times of the controller bymonitoring the outputs. At the appropriate percentage of irrigating astation matching the daily water budget percentage, the contact opensthereby shortening each station run time. If the accumulation method isused, the module microprocessor determines if the accumulated dailywater budget percentages have reached the threshold level. If they havenot, the percentages continue to accumulate until the threshold level isreached, then irrigation is allowed. If the threshold has been reached,irrigation is allowed. Of course, as in other embodiments, irrigationmay be suspended from input from any of the irrigation shut down sensorssuch as a rain sensor, freeze sensor, or wind sensor.

FIG. 11B is a flow chart of an exemplary embodiment illustrating thedual use of smart irrigation or restricted watering schedules dependingupon the time of the year or calendar dates. A smart controller isprovided which may be ET based, historical ET based, water budgetpercentage based, soil moisture based, etc. The smart technology of thecontroller is not limited to the water budget methods of the presentinvention, but may receive, for example and without limitation, wirelessreal time ET data (current ET data is not used by any embodiment of thepresent invention), environmental sensor data from which ET₀ may bedetermined or calculated (ET is not calculated by any embodiment of thepresent invention), or soil moisture sensor data. The flow chartspecifically shows ET-based and water budget percentage flow charts.

Regardless of the smart technology present, in this exemplary embodimentif the calendar shows that watering restrictions are appropriate forthat day or time period of the year instead of the available smarttechnology, the controller microprocessor determines if it is an allowedday of the week, time or day, or day of the month. If it is, then thecontroller irrigates on that day. If not, it waits until an allowedtime, then allows irrigation.

However, in this exemplary embodiment, if the smart technology withinthe smart controller is ET-based (which smart technology itself is notwithin the scope of this invention), illustrated on the left path ofFIG. 11B, the calendar is checked to see whether the current date isappropriated for ET-based smart irrigation, or subject to restrictedwatering schedules. If ET-based smart technology is appropriate for thatday, the controller determines if the ET has accumulated to a setthreshold. If it has reached that threshold, irrigation occurs accordingto the prescribed smart ET calculations. If the threshold has not beenreached, the controller waits until it is reached, then irrigates.

Alternatively, in this exemplary embodiment, if the smart technology inthe controller is water budget percentage based (which smart technologyis within the scope of this invention), two paths are available,illustrated on the center and right paths of FIG. 11B. Using the centerpath of daily water budgeting percentages, the calendar is first checkedto see whether the current date is appropriated for water budgetingsmart irrigation, or subject to restricted watering schedules. If waterbudgeting smart technology is appropriate for that day, irrigation isallowed according to the water budget percentage for that day.

In a variation of the water budgeting embodiment, if the smarttechnology is water budgeting with accumulation (right path of FIG.11B), once again the calendar is checked to determine if it isappropriate for smart technology or restricted schedules. If waterbudgeting smart technology is appropriated for that day, andaccumulation water budgeting smart technology is used, the water budgetaccumulation is checked to see if it has reached the threshold. If ithas, irrigation is permitted. If it has not, the controller waits untilthe accumulation reaches the threshold, then irrigation takes place.

It is to be appreciated that in alternative embodiments not illustratedin FIGS. 11A-B, the use of automatic watering restrictions and automaticsmart technology may be combined. For example, and without limitation,if a daily water budget percentage is determined for a particular day,but watering is restricted (not allowed) on that day during the hours of7:00 a.m.-6:00 p.m., embodiments of the present invention mayautomatically change the watering start time to an allowed time (e.g.after 6:00 p.m.), and at that time also cause the watering run time(s)to be adjusted according to the daily percentage.

In alternative embodiments of FIG. 11B, a plug-in with the restrictedwatering schedule and calendar could be used to communicate with thesmart controller.

In the flow chart of FIG. 11B, a third branch could be provided if thesmart technology is soil moisture sensor based. In that case, the smarttechnology (default program) would be based on a soil moistureindication which would be used at certain times of the year, while atother times of the year, watering restrictions may be imposed.

FIG. 12 is an exemplary flow chart from FIG. 4A of the '368 patentdepicting alternative implementations of a water budget (station runtimes, accumulation, and watering intervals). If these implementationsare used in an irrigation controller, it is first programmed with itspreliminary irrigation schedule and the schedule of allowed wateringtimes (e.g., municipal watering restrictions). If the method of dailywater budget calculations is selected, the water budget calculation isdetermined in the controller and adjusts the preliminary station runtimes, and checks to see if it is an allowed watering day. If not, itwaits until an allowed watering day is reached. Alternatively, ifwatering is set to begin at a time that is not allowed on a wateringday, the controller may automatically change the station start timesuntil a time when watering is allowed on that day.

In the accumulation mode, the controller is again programmed with itspreliminary irrigation schedule and the schedule of allowed wateringtimes restrictions. A water budget is determined periodically with orwithout using historical ET. If the water budget does not exceed the setthreshold, it continues to accumulate until the threshold is reached orexceeded. When the threshold is reached, the schedule of allowedwatering times is consulted and if watering is allowed, the controllerinitiates watering. If not, it waits until allowed, or changes the starttime(s) until an allowed time.

In another mode, the determined water budget projects the wateringinterval and initiates irrigation based on this projected interval andthe allowed watering times.

FIGS. 13A and 13B represent exemplary embodiments of add-on modules (theletters “TBM” in the figures refer to “temperature budgeting module”)that monitor the outputs of an existing controller in two ways. In FIG.13A, each 24 VAC station output from the controller is monitored and thesummer or preliminary station run times are learned by the module. Uponsubsequent operation of the learned station, the valve operation islimited by the water budget determined for that day by the module. Forexample if the preliminary station run time for station 2 was twelveminutes, and the water budget for that day is 20%, the module wouldallow this station to run for 2.4 minutes before it is cut off.

In the version of FIG. 13B, each station is still monitored by theadd-on, but instead of each station being individually controlled,control is affected by breaking the common line to all stations. Thismay result in certain stations coming on or off if two or more stationsare being operated simultaneously. The advantage of the first version isindependent station control, while the advantage of the second issimpler module circuitry and cost.

FIG. 14 illustrates an embodiment of a self-contained irrigationcontroller mounted in a pedestal. This can be a stand-alone AC poweredcontroller, a DC or solar or ambient light powered controller, or partof a remotely located controller as part of a central system. Theinnovative matter is that the smart controller is self-contained. Thesensor required in some water budgeting embodiments is provided nearbyand communicates with the controller microprocessor and associated datastorage device, if needed. Placing the temperature sensor near groundlevel provides a close approximation of ambient temperature reading. Anoptional internal rain sensor may provide shut down in case ofprecipitation, and the temperature sensor can also provide shutdown incase of near freezing temperature. In use, the operator programs thecontroller as any other conventional system. The water budgetingtechnology is either incorporated into the controller microprocessor, orcommunicated to the controller from a plug-in, or broadcast to it from acentral location. Depending upon the method used (e.g. daily oraccumulated water budgets), the controller irrigates accordingly. Ifrestricted water schedules are also incorporated, this self-containedcontroller responds in the same manner as other embodiments where suchrestrictions are automatically implemented. As an option, thisself-contained controller may not even require external AC power. It canbe battery powered, solar powered, or ambient light powered to make ittotally self-contained. If desired, additional sensor data can beprovide to further modify the water budget, through additional sensorsassociated with the controller, or broadcast to it by wireless means.

FIG. 15 illustrates an exemplary computer screen from which a customrestricted watering schedule can be developed and provided to acontroller, add-on plug-in, or other device to allow for automatedseasonal watering restriction changes. This screen can also beprogrammed to provide for alternating between smart watering orrestricted watering. This type of programming could be done on thecomputer, or directly in a smart controller, add-on or plug-in or otherdevice. By way of example only, and without limitation, and referringparticularly to the exemplary embodiment of FIG. 15, restricted wateringand/or alternate smart/restricted schedules may be implemented asfollows:

-   -   1. A small programming memory device can be provided with the        controller, add-on, plug-in or other device with a USB        connector.    -   2. If the restricted watering schedule is not pre-programmed        into the controller, add-on, plug-in, or other device, the user        is instructed to access a site on a PC or MAC that displays a        computer screen, such the exemplary screen shown in FIG. 15.    -   3. The user clicks on the “MODIFY” button and begins to enter        his restricted schedule. He identifies the water district or        municipality and if his designated watering group (if any) is an        even or odd street address or any other watering group. If the        computer recognizes the water district, the screen could fill        itself in completely automatically.    -   4. If the entered water district is not in the site data base,        the user can then complete his own schedule by entering the        information required such as the seasonal dates and the allowed        watering times of the day for the different seasons.    -   5. Once the screen is either automatically filled out or        manually programmed by the user, the user clicks on the “DONE”        button to save the information.    -   6. If alternating use of smart or restricted watering is to be        implemented, the bottom section of the computer screen is filled        out as well. This provides dates during the year when smart        technology is automatically implemented by zip code or location,        and the dates during the year when restricted schedules are to        be implemented.    -   7. The small data storage device is plugged into one of the        computer's USB ports or other data access port.    -   8. The user then clicks on the “DOWNLOAD” button.    -   9. When the download has been completed and confirmed, “DOWNLOAD        VERIFIED” shows on the screen.    -   10. The programming device is removed from the computer and        plugged into the controller, add-on, plug-in or other device.    -   11. In some embodiments, the host device acknowledges receipt of        the information by indicating “SCHEDULE ENTERED” or the like.    -   12. The controller, plug-in, add-on or other device will then        allow irrigation according to the restricted water schedule dual        restricted/smart use.    -   13. If the restricted schedule changes, the small plug in memory        device can be re-programmed on the PC or MAC by clicking on the        “MODIFY” button which will allow changes to the original        program.

It is to be appreciated that the above scenario is by way of example,and that the input/updating of restricted watering schedules into acontroller, add-on, plug-in or other device may be accomplished innumerous other ways, including manually, wirelessly, via computerdownload, over the internet, etc. For example, and without limitation,the following additional or alternative means of implementing restrictedwatering schedules and/or dual or alternating smart/restricted schedulesare listed below:

Some alternatives to using PC programming include, without limitation,providing the restricted watering schedules with the use of a cellphone, iPhone, iPad, notebook, notepad, laptop computer or otherelectronic communication device. An application made for the input ofrestricted watering schedule data could be made for use with thesemobile devices as well. An example could be a user accessing saidapplication with an iPhone and entering a restricted water schedule oralternating use. The user could then send this information wirelessly tothe controller, add-on, or plug-in device to allow implementation ofsuch restricted watering schedule automatically.

Other examples include without limitation, a user accessing softwaredesigned to obtain restricted watering data. The user could input therestricted watering data into his desktop, laptop, iPad, iPhone,notebook computer, or other similar device. Next he would send this datato his controller wirelessly, through a USB connection, or another meansto his controller, add-on, or plug-in device.

Other examples include without limitation, a web site designed to gatherrestricted watering schedules. A user could input his restrictedwatering data from his laptop or notebook computer, cell phone, iPhone,iPad, etc. based on his local watering rules. The information could thenbe transmitted wirelessly or through a USB connection to a controller,add-on, or plug-in device. It is to be appreciated that the aboveexamples are a non-exhaustive list of potential computerizedtransmission means by which restricted watering schedules or other datamay be provided to embodiments of central units, controllers, add-onsand/or plug-ins of the present invention.

In other embodiments, the controller, add-on, plug-in or other devicemay be used as an alternating device between smart technology andwatering restrictions. By way of example, and without limitation, suchadditional implementation could be accomplished as follows:

-   -   1. Enter the local zip code if water budgeting is used;    -   2. Enter the month and day that smart watering is to start and        end;    -   3. Enter the month and day that restricted watering is to start        and end.

One reason to allow the device to alternate between automatic wateringrestrictions and smart technology is to make it possible to use smarttechnology during certain times of the year (with no wateringrestrictions), and use watering restrictions alone during the rest ofthe year. Similarly, some locations may require smart technology duringcertain times of the year with no restrictions during others. Theseembodiments also allow for automatically selecting the appropriaterestricted water schedule for that time frame (e.g., the “winter”schedule of FIG. 6A during November-February, the “spring/fall” scheduleduring March-April and September-October, and the “summer” scheduleduring May-August). These embodiments also allow the local waterdistrict, municipality or other authority to change or update theirrestricted schedules, which may be downloaded into an embodiment of thepresent invention to assure compliance. These methods can be utilized toprogram a controller, add-on, plug-in or other device. Similaradditional means of water conservation methods using cell phones,iPhones, iPads and the like as previously disclosed in the descriptionof FIG. 15 also apply in these embodiments without limitation.

It is to be appreciated that these steps, or similar ones, may also beused to instruct a controller, add-on or plug-in to automatically choosebetween a selected restricted watering schedule and smart technology.

NON-LIMITING EXAMPLES OF EMBODIMENTS OF THE PRESENT INVENTION Example 1Use of Temperature Budgeting within a Controller, without the Use of anyForm of ET

The following example is provided for illustrative purposes only andwithout limiting the appended claims. This example assumes that theoperator has already determined the preliminary irrigation scheduleusing any number of commonly available methods, such as personalexperience, or from the system designer.

Assume for the purpose of this example that an irrigation controllerembodying the present invention is to be installed in Fresno, Calif., at10:15 a.m. on Feb. 15, 2004. However, this method can be used anywherein the world. The zip code is a convenient way in the U.S. and that iswhy it is used. The operator installs the controller and enters thecurrent time, date, month and year. If he is outside the U.S., he entersthe expected average summer high temperature and the latitude. As anexample, assume that somewhere in Southern Europe, the average July hightemperature is 98° F. in July, and the latitude is 37° N. Thetemperature budgeting setup screen would then appear as follows:

-   -   Current Time/Date: 10:15 AM, Feb. 15, 2010    -   Average July High Temperature: 98° F.    -   Latitude of this Location: 37° N

The controller immediately determines from its internal look-up tablethat the average summer RA factor at this particular latitude in July is16.7. The controller then calculates the STBF to be 16.7×98=1636.6.Finally, he enters an irrigation schedule for his first irrigationstation, which for this example is six (6) minutes of watering timethree times a day.

Assume that the date is now November 2. The recorded high temperaturefor the previous period (twenty-four hours herein) was 52° F. Thecontroller lookup table indicates that the RA on this particular day is7.7. This means that the PTBF is 400 (the temperature of 52° F.,multiplied by the RA of 7.7). Dividing the PTBF by the STBF provides aWBR value of approximately 0.244, or 24.4%. The irrigation duration forthis particular period will be decreased to approximately 1.5 minutes ofwater (the 6 minute initial irrigation schedule, multiplied by the WBRvalue of 0.244=1.46 minutes of water), thrice per day.

The operator could also program the controller to suspend irrigation ifthe temperature at the beginning of an irrigation cycle is below thespecified minimum temperature, or (if a precipitation sensor isincluded) if precipitation exists during, or before, an irrigationcycle. For example, assume that precipitation exists during the secondwatering irrigation time above. The precipitation sensor detects theexistence of such precipitation, and communicates such existence to thecontroller, causing the controller to cancel the previously scheduledsecond watering duration of 1.5 minutes. Further assume that the minimumtemperature is set at 35° F. Further assume that, at the beginning ofthe third irrigation time above, the current temperature was 34° F. Thiswould cause the controller to cancel the previously scheduled thirdwatering duration of 1.5 minutes.

As an even more user friendly alternative, the zip code or locationspecific historic environmental data and date and time is providedwithin the controller, add-on or plug-in.

This simple, intuitive, cost-effective, user-friendly approachencourages significantly higher long-term consumer participation, makingit possible to save most of the wasted landscape water and subsequentrunoff, which in California would be over one million acre feet. Theadditional infrastructure and environmental benefits of this waterconservation have previously been enumerated by the EPA, as describedherein.

Example 2 Use of Stored Historical ET in Determining the Water BudgetPercentage without Calculating ET within the Embodiments

The historical ET data shown in FIG. 1A is the same as FIG. 1 of parentU.S. Pat. Nos. 7,058,478, 7,266,428, 7,844,368 and of pendingapplication Ser. No. 12/955,839 from which this application claimspriority. While no ET calculation is performed by any embodiment of thepresent invention, stored historical ET data can nevertheless be used inembodiments of the present invention in determining the water budgetpercentage (WBR). It is to be appreciated that historical ET is onlyused—not calculated—by any of the embodiments herein. Stored historicgeo-environmental data could consist of monthly, weekly, or daily ETdata and temperature data for a given geographic location, and may beidentified, for example, by the zip code or latitude and longitude, etc.

The following example of determining a water budget percentage usinghistoric ET is provided for illustrative purposes only and withoutlimiting the appended claims. Assume that the historic ET data for aspecified location (determined by a zip code or other locationdesignation) is an ET of 14.0 inches for July, and the historic ET forthe month of September is 10.8 inches. Assume that the historic Julyaverage high temperature is 97° F., and that the temperature for aparticular day in September is 84° F. The water budget percentage forthat day in September, using historical ET, would be determined bymultiplying the current (September) high temperature times historic ETfor the current month, divided by the average high temperature for Julytimes historic average ET for July, as follows:

(84×10.8)/(97×14.0)=66.7%.

By way of comparison, determining the water budget percentage usingtemperature budgeting would need the Ra factors for July and September,which are 16.7 and 12.8 respectively. So the comparative calculationwould be:

(84×12.8)/(97×16.7)=66.4%.

This example shows that the difference between the calculated waterbudget percentages is insignificant (66.7%−66.4%), such that eithercalculation may be used to reach a useful result without the need tocalculate ET. The determined water budget percentage is then used toeither adjust the run times periodically (e.g., daily) by the calculatedpercentage, or adjust the irrigation schedule by accumulating thepercentage until a minimum threshold is reached. While historic monthlyaverage ET data is used in this example, weekly or daily ET historicdata may also be used.

As can be seen in this example, historic ET may be substituted for theequivalent ET expressed as the Ra factor. However, the methods ofdetermining the water budget ratio or percentage is not to be limited bythis or any specific equation. The water budget ratio is determined bycomparing current geo-environmental sensor data to storedgeo-environmental data and using it to adjust the irrigation schedule,or run times without calculating ET within the embodiments. Thedetermined or calculated periodic water budget can also be applied dailyto adjust the station run times or accumulated until a threshold levelis reached to adjust the watering interval. While this example usesmonthly historic ET, weekly or daily ET may also be used for specificdays of the month for a specific location.

As noted previously, some embodiments do not require any form of ET.However, the use of historic ET, for example, as a substitute for Ra(the equivalent evaporation), is a viable alternative as illustrated inFIG. 1 of each of the parent patents and as noted by the SWAT results ofFIGS. 5A, 5B, 5C, and the above comparison. The temperature budgetingmethods (which may include historic ET) provide extremely reliablewatering adjustment tools without all the ET variables nor any need tocalculate ET within the embodiments of the present invention. FIGS.5A-5C represent two irrigation controllers and an add-on, all using thepreferred temperature budgeting method. The use of historical ET as analternate method may appropriately still be called “temperaturebudgeting” because it only requires a minimum of one current sensor(temperature) data with the substitution of historic ET for theequivalent evapotranspiration (Ra).

As with other embodiments, once the water budget is determined, it canthen be used to automate the existing manual water budget feature of acontroller, or determined externally and communicated to a controllermicroprocessor by means of a plug-in type of add-on. Alternately, anadd-on that attaches to the output of any controller can accumulate thewater budget percentages and allow watering when a threshold is reached.A minimum of at least one environmental sensor is required (preferablytemperature) although additional sensors such as a rain, wind, solarradiation, soil moisture, soil temperature, and relative humiditysensors may also be provided to allow for more exact calculations ifneeded. The current or real time sensor data may be provided by wired orwireless means.

Similar calculations can be performed using one of the stored historicalET curves as shown in FIG. 1 a which are zip code specific, althoughsimilar ET historical curves may be used regionally.

It should be noted that in this embodiment, the stored historic ETmethod does not necessarily require the use of the Ra because Ra isalready expressed as an equivalent evaporation as noted at the top ofFIG. 2 in the same units of measurement as ET, in this case millimetersof water. Peak historic ET data is used for that zip code location and adaily, weekly, or monthly historic ET value is used along with historictemperature data and current temperature data in an equation similar tothe above example to determine or calculate the water budget.

To re-emphasize, a water budget percentage is determined or calculatedwithout calculating ET even if the stored data from which the percentageis determined may consists of historic ET data. The resulting waterbudget is then used to either adjust the irrigation schedule, wateringinterval, or station run times accordingly.

Example 3 Determining a Water Budget Percentage Using Soil MoistureSensors

The following example of determining a water budget percentage usingsoil moisture sensors is provided for illustrative purposes only andwithout limiting the appended claims. In soil moisture sensingapplications, a similar (but not identical algorithm) may be used. Forexample, historic soil temperature and moisture data can be provided toan irrigation or soil moisture sensing controller. Current soiltemperature and moisture data is then provided on a real time basis fromsoil sensors and compared to the historic data for that location forthat time or day of the year. A water budgeting percentage can thereforebe calculated by comparing the current soil moisture and temperaturedata to historic soil moisture and temperature data for that location,which are considered geo-environmental data. This calculation yields apercentage which can then provide the amount of irrigation needed toreplenish the root zone to a pre-determined level. More specifically, ifthe minimum root zone dry level is set to 20% moisture, and the maximumis set to 90%, the comparison of current to real time sensor data tohistorical data may say to activate the station run time by 70% of thesummer run time to fill the root zone to the 90% level.

Example 4 Using a Plug-in Device to Determine and Implement a WaterBudget Percentage

The following example is provided for illustrative purposes only andwithout limiting the appended claims. An existing (non smart) irrigationcontroller is provided with an input port to its microprocessor. Aplug-in device is attached in communication with that microprocessorthrough the input port. One or more environmental sensors providecurrent or real time weather data to that plug-in by wired or wirelessmeans. Those sensors may consist of ambient temperature, solarradiation, wind, relative humidity, precipitation, soil moisture, soiltemperature, or combinations thereof. The plug-in module either ispre-programmed with local historical environmental data accessed bymeans of a location identifier (such as a zip code or latitude andlongitude, or regionally), or such historical data is input. Thathistorical (stored) data may consist of temperature, solar radiation,wind, relative humidity, or precipitation, or historic ET, soilmoisture, soil temperature, or combinations thereof. Periodically, thesensors provide environmental data to the plug-in module. That real timedata is compared to the stored geo-environmental data and a water budgetis determined according to one of the methods outlined herein. Thiswater budget is communicated to the host existing controllermicroprocessor which then either adjusts the set summer run times or thepreliminary schedule according to the determined water budget percentageon a daily basis or an interval determined by accumulation.

Example 5 Using the Accumulation Method in a Controller, Add-on orPlug-in

The following example is provided for illustrative purposes only andwithout limiting the appended claims. An irrigation controller isprogrammed with a preliminary irrigation schedule using personalexperience, internet based guidelines, with professional assistance orthe like. A zip code or other location data is entered into thecontroller, add-on or plug-in from which historic data for that locationis obtained such as latitude, temperature, ET, relative humidity, wind,precipitation, soil moisture, soil temperature, or combinations thereof.One or more environmental sensors are placed in communication with thecontroller, add-on or plug-in to provide current or real time data. Thereal time data is compared to the stored historic data to determine aperiodic (preferably daily) water budget percentage. The controller,add-on or plug-in is programmed to accumulate the periodic percentagesuntil a threshold is reached. For example, an accumulated percentage ofat least 40% may be required before irrigation takes place. A minimumthreshold percentage assures adequate penetration of the root zone. If aplug-in is used, the determined water budget percentages arecommunicated to the controller which may have been programmed with theminimum threshold.

In the case of an add-on, the existing irrigation controller isprogrammed with its preliminary or summer irrigation schedule andprogrammed to irrigate on given days. The add-on is mounted near thecontroller and has an internal cut off switch that is capable ofbreaking the common line. The add-on can be provided with a locatormeans such as a zip code which identifies the historical environmentaldata for that location, such as temperature, historic ET, relativehumidity, solar radiation, wind, soil, or combinations thereof. One ormore environmental sensors provide real time data to the add-on. Theadd-on periodically (preferably daily) determines the water budget. As adevice that breaks the common line, the add-on could accumulate thedaily water budget percentages until the threshold is reached, which maybe for example 100% of the summer run times, at which time the commonline is closed to allow irrigation to occur. On that day, the controlleris allowed to run its summer irrigation schedule, assuming it is also anallowed watering day.

As an accumulation example, if it were November, the daily determinedpercentage may be 22% on a given day. No irrigation will be allowed thatday. It may take 5 days or more during the cooler times of the year forthe water budget accumulation to reach the 100% threshold. So the add-onwill break the common line and prevent the controller from irrigating anaverage of four out of every five days in this example. If a restrictedwatering schedule is also imposed into the add-on simultaneously, themodule will withhold irrigation until both the threshold is reached andan allowed watering day/time is reached. In this case, the module willcontinue accumulating the daily water budget percentages until anallowed watering day is reached. Most commonly, however, the add-on orplug-in or controller will either be used as a smart device, or as a TOUunit, not both together. The circumstances of the availability of water,and infrastructure capabilities will generally dictate which method isbest for that municipality or water district.

Example 6 An Automated Restricted Watering Schedule in a Smart orConventional Controller

The following example is provided for illustrative purposes only andwithout limiting the appended claims. A conventional or smart irrigationcontroller is located in a municipality which restricts irrigations tocertain times of the day, or certain days of the week, or certain daysof the month, depending on the street even or odd address or some othergroup designation. Municipal landscape watering restrictions have beencommon for decades, but always required manual initial setting andmanual adjustment for seasonal changes. There are two novel approachespresented here and by the parent patents regarding automated wateringrestrictions. The first is the pre-programming of multiple restrictedwatering schedules within the controller from which one can be selectedby, for example, entering a location identifier such as the name of thewater district or town, by zip code, or latitude/longitude. Thiseliminates the need to program the entire restricted schedule manuallyinto the controller, only the location. The second novelty is that oncethe schedule is selected, upon input of the date/time, the controller iscapable of automatically adjusting the allowed watering days and timesseasonally without the need for human intervention. As seen in FIG. 6B,the SNWA defines their seasons to be seasonally manually changed asfollows: “Adjust your watering clock seasonally: Sept 1, Nov 1, March 1,and May 1”. In addition, the allowed watering times also vary during thecourse of the year. For example, no irrigation is allowed from May 1until October 1, from 11 a.m. to 7 p.m. The present invention wouldautomate this requirement.

Automation of the water restriction features were proposed in the '244patent preceded by its provisional applications. In a recent study bythe SNWA, the use of an automated water restriction device reported thefollowing compliance to the restrictions shown in FIGS. 6A and 6B:During the fall, an increase from 8% to 41%, from 11% to 41% in thewinter, and from 15% to 31% in the spring. The total water savings frommanual compliance to automated compliance yielded a savings of 13% forthe three seasons reported. No report was made during the summer months.It can be assumed that automated non watering from 11 a.m. to 7 p.m.during the summer would have added to the savings. This comparesfavorably to the AquaCraft study referred to previously of 6.3% watersavings from conventional to smart ET based controllers, particularly inview of the fact that the SNWA already had a degree of compliance beforethe study with the automation.

Advantages of Having Both Smart Technology and Automated RestrictedWater Schedules Capability within a Controller, Add-on or Plug-in

Various water districts or municipalities have different existing waterrelated considerations and conditions:

-   -   1. Some areas may have plentiful stored water, but limited        pumping and delivery capability. This limitation could result in        ineffective delivered water pressure, decreasing irrigation        efficiency and increasing the watering times to account for this        deficiency. At the same time, increased watering could lead to        runoff pollution, and over watering in certain landscape zones        leading to diseases.    -   2. In areas where the infrastructure is currently adequate,        rapidly increasing housing and population would reduce the        ability of the existing infrastructure to handle future needs,        leading to significant investment in infrastructure upgrading        needs.    -   3. Some areas have an adequate infrastructure, but limited water        supply from drought or limited water storage capacity.    -   4. Some areas have both a strained infrastructure and a limited        water supply.

If the water supply is adequate, the intent is to reduce the load on theinfrastructure. This can be accomplished by regulating the allowedwatering days of the week or days of the month with even or odd addressdesignations, and limiting the times of the day to limit landscape wateruse to off-peak water demand times of the day. In general, the intent isto distribute landscape irrigation to reduce the water demand load.

If the infrastructure is adequate but water is limited, either wateringrestrictions may be implemented or smart irrigation. Unfortunately, asobserved herein, ET based controllers have gained limited acceptance,and even when used, have delivered disappointing water savings.

If the community or water district has both limited water supply andinadequate infrastructure, severely limiting landscape watering may bethe only option primarily by restricted watering schedules. This was thecase with the SNWA which tried to encourage the use of smart controllerswith rebates, with very limited success. That is why they are nowconsidering automated watering schedules based upon their recent study.

The ability to provide both smart water budget automation and automatedrestricted watering schedules provides considerable flexibility to awater district that may wish to begin with restricted schedules tosatisfy infrastructure limitations, or to convert from wateringlimitations to smart technology (water budgeting) because a simpler moreeconomical automated technology in a controller, add-on or plug-in willprovide the greatest landscape water savings, depending upon the waterconditions of the municipality.

Example 7 A Controller, Add-on or Plug with Both Temperature BudgetingTechnology and Automated Time of Use for Restricted, Allowed, or notAllowed Watering Times

The following example is provided for illustrative purposes only andwithout limiting the appended claims. A controller is programmed withits preliminary irrigation schedule. If a zip code is entered, thecontroller, add-on or plug in may automatically determine where it islocated, and then gain access to historical geo-environmental data forthat location. The unit then determines a periodic water budget, whichmay be used daily or by the accumulated method, with or without storedhistorical ET. One or more restricted watering schedules are madeavailable to the unit, and may be selected by the user or determinedaccording to user entry (zip code, date/time). The schedule appropriatefor that location could be selected by entering a location designatorfrom a list provided in the owner's manual, from an internet site, etc.An applicable restricted scheduled is then automatically selected by theunit. Based upon these restrictions, the unit would only irrigate or beallowed to irrigate based upon the selected schedule which could be timeof day, day of the week, or day of the month dependent. In otherembodiments, the local municipality may have different restrictionsdepending upon the time of the year, and the unit would select and/orchange to different restrictions when applicable at different times. Inembodiments using automatic water budgeting and automatic wateringrestrictions, the controller or add-on would automatically adjust itspreliminary schedule according to the periodic water budget, and allowwatering only on the allowed watering times of the day or watering daysof the week or days of the month, accordingly. In embodiments usingautomatic water budgeting and automatic accumulation with wateringrestrictions, the controller or add-on would accumulate water budgetsuntil a threshold is reached, and then allow watering only at the nextallowed watering time of the day, or day of the week.

It is to be appreciated that one way embodiments of the presentinvention may comply with restricted watering schedules is to changestation start times to begin at times when watering is allowed. Forexample, the start time may be set for 7:30 a.m., but local wateringrestrictions prohibit watering after 7:00 a.m. on the day watering isscheduled; in such a situation, instead of prohibiting wateringaltogether that day, embodiments of the invention may change the stationstart time to 6:00 when watering is allowed. The watering may be cut offat 7:00 a.m. when the restrictions go into effect.

Some embodiments illustrated in this example include:

-   -   1. Automated selection of one of multiple pre-programmed        restricted watering schedules.    -   2. Automated seasonal change in watering restrictions.    -   3. The use of embodiments 1 or 2 in combination with a        temperature budgeting method within a controller, add-on or        plug-in.    -   4. The combination of 1 or 2 with any smart irrigation based        controller, including ET based controllers.    -   5. An add-on that learns the summer run times and uses        temperature budgeting to modify the run times daily    -   6. An add-on, plug-in, or controller that can operate as a smart        controller during certain times of the year, and as a restricted        schedule controller during other times of the year, for example        during the summer months when watering may not be allowed during        certain times of the day as in the SNWA area.

Example 8 A Self-Contained Smart Controller

The following example is provided for illustrative purposes only andwithout limiting the appended claims. An irrigation controller islocated in an outdoor pedestal as shown in FIG. 14. The housing may bemetal or some form of plastic. The controller is programmed with asummer irrigation schedule. In a preferred embodiment, only atemperature sensor is required. This sensor is placed within thepedestal at a location where it most closely approximates the ambienttemperature (preferably at ground level). A rain sensor may beoptionally be built into the controller pedestal, as shown in FIG. 14.The smart technology of choice and/or restricted watering schedules areimplemented within the controller microprocessor. The controller thenirrigates according to its smart technology and/or the restrictedwatering schedules. If only the restricted watering schedules are used,the temperature sensor can be used as a freeze control device to shutdown irrigation before the temperature reaches freezing. The rain sensorcan shut down irrigation when there is a sufficient amount ofprecipitation. To make the controller totally self-contained and selfpowered, it may be solar, ambient light, or battery powered.

Example 9 An Add-on that Learns the Station Run Times and AdjustsIrrigation Accordingly

The following example is provided for illustrative purposes only andwithout limiting the appended claims. A conventional controller isprovided. An add-on module is provided that monitors the 24 VAC outputsof the conventional controllers and “learns” their run times. See FIGS.13A and 13B. These figures disclose two embodiments, depicted as TBMs(temperature budgeting modules). The exemplary version of FIG. 13Amonitors and learns each station run time, and on the subsequent times,cuts off each output independently according to the water budgetdetermined for that day by means of multiple cutoff switches, one foreach station. If the learned station run time for station 1 was 8minutes, and today's water budget is 25%, the module would allow valve 1to come on for 2 minutes then cut it off.

The second exemplary version is depicted in FIG. 13B. Here, each stationis still monitored and the run time learned, but the wires to each valveare in parallel with the TBM wires. The common line is broken in thiscase to all the valves at once, instead of each individual station line.Once again, the module learns the run times, and on subsequent stationactivations cuts off each station operation, based on the water budget,by cutting off the common line.

The advantage of the first version is that each station can be operatedindependently. However, additional electronic circuitry and one outputswitch is required with each station, which adds cost and size to themodule. The second version is less complicated, but if more than onestation is operated at a time, stations will need to go on and offaccording to the breaking of the common line to satisfy the full waterbudge percentage.

Example 10 Central Unit Sending Data to Remote Controller(s), Add-on(s)or Plug-in(s)

The following example is provided for illustrative purposes only andwithout limiting the appended claims. A centrally located unit isprovided with a microprocessor and a means for sending out data, suchas, without limitation, a transmitter and antenna (for broadcasting), awireless network link, an internet communication link (wired orwireless), or even hard-wired communications. One or more receivingunits (which may themselves be controllers, add-ons and/or plug-ins) areprovided as shown in FIGS. 9A-9C. The receiving units are incommunication with the central unit and may have, without limitation,radio/wireless receivers, internet connections, hard wired links, etc.In different embodiments, the central unit may address the receivingunits as a group or individually.

The various steps and apparatus of embodiments of the present inventionmay be divided between the central unit and the receiving units in amultitude of combinations. Turning first to implementation of waterbudgeting, for example, and without limitation, in some embodiments, thecentral unit may generate the water budget percentages and send them tothe receiving units for implementation. In other embodiments, thecentral unit may simply provide current environmental data to thereceiving units which themselves generate and then implement the waterbudget percentages. In other embodiments the receiving units may havetheir own environmental sensor(s) and not require anything from thecentral unit to generate water budget percentages. In some embodiments,water budget percentages may be accumulated in the central unit; inother embodiments, those percentages may be accumulated in the receivingunits. Each of these water

budgeting examples may or may not be combined with automaticimplementation of restricted watering schedules.

Turning to automatic implementation of restricted watering schedules,for example, and without limitation, in some embodiments, the centralunit may receive several sets of watering restrictions (e.g., differentrestrictions being applicable at different seasons of the year), and thecentral unit decides which restrictions are currently in effect andsends those to the receiving units. In other embodiments, the centralunit sends all of the restriction sets to the receiving units whichthemselves determine which one is currently applicable.

In very simple embodiments, the central unit may perform numerousfunctions and simply send a “ok to water” or “not ok to water” signal(or a “start watering”/“stop watering” signal) to the receiving units.It is to be appreciated that these are only some examples of how thesteps and apparatus of embodiments of the present invention may bedivided up between the central unit and the receiving units.

Typical Instructions for Automated Selection, Programming, andImplementation of Restricted Watering Schedules in a Smart orConventional Controller, Add-on or Plug-in:

It is important to note that the following exemplary procedure forautomatically selecting, programming, and seasonally changing restrictedwatering schedules is without limitation to the claims herein.

STEP 1: Some restricted watering schedules are pre-programmed into yourcontroller, add-on or plug-in. Go to that function on your device andenter your zip code to determine if your restricted schedule ispre-programmed. If it appears, enter it to enable it.

STEP 2: Enter your group designation if applicable (even, odd, groupdesignation, etc. . . . ) and your drought stage if specified.

STEP 3: If your allowed watering schedule is not available, access thedesignated site on your computer.

STEP 4: Enter your zip code on that screen and your schedule willappear. Enter your designated watering group and drought stage ifapplicable.

STEP 5: If your restricted schedule has changed, you may manually updatethe schedule on the screen and click on the “UPDATE” button.

STEP 6: Insert your programming device into one of the computer's USBports and click on the “DOWNLOAD” button.

STEP 7: Remove the programming device and plug it into the hostcontroller, add-on or plug-in module. The schedule or updated schedulewill automatically be implemented, including seasonal changes asspecified by the water district or municipality.

Dual Use of Water Budgeting or any Smart Technology (Including ET Basedor any Other Smart Technology or Soil Moisture Sensing Method) andRestricted Watering Schedules

Assume that in the SNWA area, it would be beneficial to minimizeevaporation during the summer months. As noted in FIG. 6B, from May 1until October 1, no watering is allowed daily from 11 a.m. to 7 p.m. Anembodiment of an add-on, plug-in, controller or other device could beprogrammed as follows to maximize irrigation efficiency:

-   -   1. If the combination of any smart water technology and watering        restrictions is in a controller, it may be programmed to operate        as a smart controller in the fall, winter, and spring months.        However, during the summer, since it is likely that most days in        the Southern Nevada climate would require nearly 100% irrigation        which would save little or no water, this controller embodiment        automatically switches to the watering restrictions mode (TOU)        to prohibit irrigation, for example, from 11 a.m. to 7 p.m. to        minimize evaporation.    -   2. If the combination of smart water technology and watering        restrictions is in a plug-in embodiment, the irrigation schedule        determined by smart technology (of the present invention or        otherwise) is communicated to the controller during the fall,        winter, and spring, and automatically replaced with the limited        allowed watering times of the day during the summer.    -   3. If the combination of smart technology is in an add-on        embodiment, the add-on would automatically allow irrigation when        either the accumulated percentages or the ET have reached their        threshold during the fall, winter, and spring, then        automatically convert to the watering restrictions during the        summer by opening the contact (preventing irrigation) from 11        a.m. to 7 p.m. each day.    -   4. If the combination is done as a central system embodiment,        the embodiment automatically switches from smart technology        during fall, winter, and spring to time of use during the        summer.

The ability to have both smart technology and time of use capability inone controller, add-on or plug-in as well as a central system offers awide range of capabilities to suit the region's conditions of wateravailability and infrastructure capabilities.

It is to be understood that variations and modifications of theembodiments of the present invention may be made without departing fromthe scope thereof. In particular, the scope of the invention includesembodiments having different combinations of the features and elementsdisclosed herein. It is also to be understood that the present inventionis not to be limited by any of the particular embodiments, examples,illustrations, equations, or specific variables disclosed herein, butonly in accordance with the appended claims when read in light of theforegoing specification.

1-260. (canceled)
 261. A method of determining a current water budgetpercentage to be used in irrigation comprising the steps of: a.providing historical geo-environmental data for a location; b. providingcurrent environmental data for said location; c. comparing said currentenvironmental data to said historical geo-environmental data todetermine said current water budget percentage without calculatingcurrent reference evapotranspiration.
 262. The method of claim 261wherein said historical geo-environmental data is selected from thegroup of evapotranspiration data, solar radiation data, precipitationdata, ambient temperature data, wind data, relative humidity data, soiltemperature data, soil moisture data or combinations thereof.
 263. Themethod of claim 261 wherein said current environmental data is selectedfrom the group of ambient temperature, precipitation, solar radiation,wind, relative humidity, soil moisture, soil temperature, orcombinations thereof.
 264. The method of claim 261 wherein said waterbudget percentage is determined according to one of the group of: withina controller, in a plug-in module, in an add-on module, and from acentral location.
 265. The method of claim 261 wherein said currentreference evapotranspiration data is calculated using one of the groupof the Pennman-Monteith equation and the Hargreaves equation.
 266. Themethod of claim 261 comprising the additional step of automaticallymodifying at least one irrigation schedule of a controller using saidpercentage.
 267. The method of claim 261 comprising the additional stepof automatically modifying at least one station run time of a controllerusing said percentage.
 268. The method of claim 261 wherein said currentenvironmental data is received from a temperature sensor.
 269. Anirrigation control unit comprising: a. a microprocessor; b. at least oneenvironmental sensor in communication with said microprocessor; and c.programming in said microprocessor to determine a water budgetpercentage without calculating current reference evapotranspiration bycomparing data from said at least one environmental sensor to storedhistorical environmental data within said microprocessor.
 270. Theirrigation control unit of claim 269 wherein said environmental sensoris selected from the group of ambient temperature, soil temperature,soil moisture, solar radiation, wind, relative humidity, precipitation,and combinations thereof.
 271. The irrigation control unit of claim 269wherein said stored historical environmental data is selected from thegroup of ambient temperature, precipitation, solar radiation, wind,relative humidity, soil moisture, soil temperature, evapotranspiration,and combinations thereof.
 272. The irrigation control unit of claim 269further comprising a controller.
 273. The irrigation control unit ofclaim 269 further comprising a plug-in module in communication with acompatible controller.
 274. The irrigation control unit of claim 269further comprising a module attached to at least one output of anirrigation controller.
 275. The irrigation control unit of claim 269further comprising a central irrigation system.
 276. The irrigationcontrol unit of claim 269 wherein power is supplied by one of the groupof AC, DC, battery, solar, and ambient light.
 277. A method ofautomating a water budget feature of a controller comprising the step ofperiodically determining a water budget percentage to be used by saidcontroller by comparing current environmental data for a location tostored historic geo-environmental data for said location withoutcalculating current reference evapotranspiration data.
 278. The methodof claim 277 wherein said current environmental data is selected fromthe group of ambient temperature, solar radiation, relative humidity,wind, soil moisture, soil temperature, precipitation, and combinationsthereof.
 279. The method of 277 wherein said historic geo-environmentaldata is selected from the group of evapotranspiration, ambienttemperature, solar radiation, wind, precipitation, relative humidity,soil moisture, soil temperature, and combinations thereof.
 280. Themethod of claim 277 wherein said water budget determination is performedaccording to one of the group of: in said controller, in a module incommunication with said controller, from a central location andcommunicated to said controller, and in said controller wherein saidcontroller is self-contained and ground mounted.